openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r993849 - in /websites/staging/openoffice/trunk/content: ./ pmc-faqs.html
Date Tue, 26 Jul 2016 20:49:17 GMT
Author: buildbot
Date: Tue Jul 26 20:49:17 2016
New Revision: 993849

Staging update by buildbot for openoffice

    websites/staging/openoffice/trunk/content/   (props changed)

Propchange: websites/staging/openoffice/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 26 20:49:17 2016
@@ -1 +1 @@

Modified: websites/staging/openoffice/trunk/content/pmc-faqs.html
--- websites/staging/openoffice/trunk/content/pmc-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/pmc-faqs.html Tue Jul 26 20:49:17 2016
@@ -49,7 +49,18 @@
   <div id="clear"></div>
   <div id="sidenav">
-    <h1 id="general">General</h1>
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent link">&para;</a></h1>
 <li><a href="/index.html">About</a></li>
 <li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
 <li><a href="/press.html">Press</a></li>
 <li><a href=""> website</a></li>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community" title="Permanent
 <li><a href="/get-involved.html">Get Involved</a></li>
 <li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
 <li><a href="/people.html">People</a></li>
 <li><a href="/community-faqs.html">Community FAQs</a></li>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development" title="Permanent
 <li><a href="/source.html">Source Code</a></li>
 <li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
 <li><a href="/contributing-code.html">Contributing Code</a> </li>
 <li><a href="/developer-faqs.html">Developer FAQs</a></li>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink" href="#project-management-pmc"
title="Permanent link">&para;</a></h1>
 <li><a href="">Project Blog</a></li>
 <li><a href="/pmc-faqs.html">PMC FAQs</a>  </li>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a class="headerlink"
href="#the-apache-software-foundation" title="Permanent link">&para;</a></h1>
 <li><a href="">Website</a></li>
 <li><a href="">Donations</a></li>
@@ -98,7 +109,18 @@
   <div id="contenta">
     <h1 class="title">PMC FAQs</h1>
-    <p>Here are a number of FAQ's about how the Apache OpenOffice project governance
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<p>Here are a number of FAQ's about how the Apache OpenOffice project governance works.</p>
 <div class="toc">
@@ -119,18 +141,19 @@
 <li><a href="#voting">How and when to vote?</a></li>
+<li><a href="#release_managers">Information for Release Managers</a></li>
-<h1 id="pmc">What is the PMC?</h1>
+<h1 id="pmc">What is the PMC?<a class="headerlink" href="#pmc" title="Permanent
 <p>The Project Management Committee (PMC) is the government of the project. The committee
is responsible for the
 project and decides what to do and which direction to go.
 <br> (<a href="">see
here for a list of PMC members</a>)</p>
-<h1 id="moderator">Who is the Admin/Moderator/Owner for X?</h1>
+<h1 id="moderator">Who is the Admin/Moderator/Owner for X?<a class="headerlink"
href="#moderator" title="Permanent link">&para;</a></h1>
 <p>Although Apache projects have few formal roles, there are some technical 
 subsystems which have admin or similar roles filled by project volunteers.  If you
 have a question with one of these systems, these are the people you might want to
 contact first, before escalating to Apache Infrastructure.</p>
-<h2 id="mailing-lists">Mailing lists</h2>
+<h2 id="mailing-lists">Mailing lists<a class="headerlink" href="#mailing-lists"
title="Permanent link">&para;</a></h2>
 <p>Each mailing list has one or more moderators. See the <a href="mailing-lists.html">Mailing
List page</a> for how to contact a moderator.</p>
 <p>Responsibilities of mailing list moderators include:</p>
@@ -141,9 +164,9 @@ allow the valid messages through.</li>
 <li>For private lists, approve subscription requests for authorized subscribers only.</li>
 <li>When needed, escalate technical issues to Infra and privacy issues to the PMC.</li>
-<h2 id="blog">Blog</h2>
+<h2 id="blog">Blog<a class="headerlink" href="#blog" title="Permanent link">&para;</a></h2>
 <p>Blog authors: You must be a committer. To establish a Roller account <a href="">contact
Infrastructure</a>. </p>
+<table class="table">
@@ -186,7 +209,7 @@ allow the valid messages through.</li>
 <p>Blog admins: Admins authorize new authors once they have first established a Roller
account. </p>
+<table class="table">
@@ -204,21 +227,21 @@ allow the valid messages through.</li>
-<h2 id="bugzilla">Bugzilla</h2>
+<h2 id="bugzilla">Bugzilla<a class="headerlink" href="#bugzilla" title="Permanent
 <p>There are two admins on the PMC:  Rob Weir, Herbert Duerr.</p>
-<h2 id="svn">SVN</h2>
+<h2 id="svn">SVN<a class="headerlink" href="#svn" title="Permanent link">&para;</a></h2>
 <p>All committers have equal access.  If you need to do something beyond ordinary committ
 rights, such as importing a dump file, <a href="">enter
a JIRA issue</a> with Apache Infra.</p>
-<h2 id="confluence-mediawiki-and-forums">Confluence, MediaWiki and Forums</h2>
+<h2 id="confluence-mediawiki-and-forums">Confluence, MediaWiki and Forums<a class="headerlink"
href="#confluence-mediawiki-and-forums" title="Permanent link">&para;</a></h2>
 <p>Registered users on any of these services generally have equal access.
 Contact the admins for these services using the links provided for the service.</p>
-<h2 id="google"><a href="">Google
+<h2 id="google"><a href="">Google
+</a><a class="headerlink" href="#google" title="Permanent link">&para;</a></h2>
 <p>Admins: Rob Weir, Chao Huang, Don Harbison,  Juergen Schmidt,  Samer Mansour</p>
-<h2 id="facebook"><a href="">Facebook</a></h2>
+<h2 id="facebook"><a href="">Facebook</a><a
class="headerlink" href="#facebook" title="Permanent link">&para;</a></h2>
 <p>Admins:  Raphael Bircher, Shane Curcuru, Don Harbison, Samer Mansour, Juergen Schmidt,
Rob Weir, (Apache id) imacat</p>
-<h2 id="twitter"><a href="">Twitter</a></h2>
+<h2 id="twitter"><a href="">Twitter</a><a
class="headerlink" href="#twitter" title="Permanent link">&para;</a></h2>
 <p>Admins: Rob Weir</p>
-<h1 id="participate">How to participate?</h1>
+<h1 id="participate">How to participate?<a class="headerlink" href="#participate"
title="Permanent link">&para;</a></h1>
 <p>First of all you have to think how you want to participate as we have different
 of roles like user, developer, committer. The easiest way is to use what we build as
 user. If you want to improve parts of the software, or documentation, write to our
@@ -238,7 +261,7 @@ away.  There is a <a href="https://cwiki
 <p>If 1 of the 4 statements above are true, then you can be voted in as committer.</p>
 <p>When the vote result is positive, you will be asked for some information to setup
 your committer status. <a href="">Read
the Participation guide for more information.</a></p>
-<h2 id="i-was-invitedvoted-as-committer-so-whats-next">I was invited/voted as committer,
so whats next?</h2>
+<h2 id="i-was-invitedvoted-as-committer-so-whats-next">I was invited/voted as committer,
so whats next?<a class="headerlink" href="#i-was-invitedvoted-as-committer-so-whats-next"
title="Permanent link">&para;</a></h2>
 <p>The following is a brief summary of what to expect as committer:</p>
@@ -297,12 +320,17 @@ instructed.</p>
 <p>See the <a href="">Guide
for new committers</a> and the <a href="">Committers'
FAQ</a> for more information.</p>
-<h1 id="voting">How and when to vote?</h1>
+<h1 id="voting">How and when to vote?<a class="headerlink" href="#voting" title="Permanent
 <p>Voting is done when a formal decision has to be made or due to legal reasons, e.g.,
 to vote in new members as committers. In any case avoid voting as the normal way is
 to come to a decision by discussions. The initiator is responsible for the vote,
 that means also to count the votes and present the result. Every member has 1 vote.
 <br> (<a href="">see
here for more information</a>)</p>
+<h1 id="release_managers">Information for Release Managers<a class="headerlink"
href="#release_managers" title="Permanent link">&para;</a></h1>
+<li>ASF General Information: <a href="">Publishing
+<li>The Apache OpenOffice dist area svn location containing distribution artifacts
and keys: <a href=""></a>.</li>
   <div id="footera">

View raw message