You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2011/10/23 03:07:05 UTC
svn commit: r797359 -
/websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html
Author: buildbot
Date: Sun Oct 23 01:07:04 2011
New Revision: 797359
Log:
Staging update by buildbot
Modified:
websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html
Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/ppmc-faqs.html Sun Oct 23 01:07:04 2011
@@ -96,6 +96,7 @@
</ul>
</li>
<li><a href="#voting">How and when to vote?</a></li>
+<li><a href="#status">How to I update the Podling Status File?</a></li>
</ul>
</div>
<h1 id="ppmc">What is the PPMC?</h1>
@@ -114,8 +115,8 @@ trouble subscribing or are wondering why
<ul>
<li>ooo-dev moderators are Rob Weir, </li>
<li>ooo-users moderators are Rob Weir, Simon Phipps, </li>
-<li>ooo-security is a restricted access list, with Rob Weir, Dennis Hamilton and
-Wolf Halton as members. New members can be added by consensus of the PPMC and via a
+<li>ooo-security is a restricted access list, with Rob Weir, Dennis Hamilton, Wolf Halton
+and Juergen Schmidt as members. New members can be added by consensus of the PPMC and via a
<a href="https://issues.apache.org/jira/browse/INFRA">request to Apache Infra</a>.</li>
</ul>
<h2 id="blog">Blog</h2>
@@ -222,6 +223,47 @@ to vote in new members as committers. In
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="http://incubator.apache.org/openofficeorg/docs/governance/voting.html">see here for more information</a>)</p>
+<h1 id="status">How to I update the Podling Status File?</h1>
+<p>It is important to keep our <a href="http://incubator.apache.org/projects/openofficeorg.html">Status File</a> up to date as our podling evolves toward graduation.
+Examples of things that should be updated include:</p>
+<ol>
+<li>When a new mailing list is created</li>
+<li>When a new committer is announced</li>
+<li>When the podling has made a release</li>
+<li>When the podling has submitted a new report</li>
+<li>Other newsworthy accomplishments </li>
+</ol>
+<p>Updating the status report is not very difficult, though it is not as easy as updating a wiki or a web
+page via the CMS. But is certainly straightforward if you have a Linux desktop.</p>
+<p>First, check out the website source:</p>
+<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/</span><span class="n">public</span><span class="o">/</span><span class="n">trunk</span> <span class="n">incubator</span>
+</pre></div>
+
+
+<p>Then edit the incubator/site-author/projects/openofficeorg.xml file in a text editor to add your new content.
+The XML should be self-explanatory. Just copy what you see there.</p>
+<p>Then go back up to the incubator dir and run ant to rebuild the site:</p>
+<div class="codehilite"><pre><span class="n">ant</span>
+</pre></div>
+
+
+<p>Take a look at the generated output in incubator/site-publish/projects/openofficeorg.html to make sure you like
+the results. Repeat the editing and running ant until you have what you want.</p>
+<p>When you are ready to commit your changes you do:</p>
+<div class="codehilite"><pre><span class="n">svn</span> <span class="n">commit</span>
+</pre></div>
+
+
+<p>Note that you will be checking in two files: the source XML in incubator/site-author/projects as well as
+the generated html in incubator/site-publish/projects</p>
+<p>One that is done you need to check out the changed html into the production website:</p>
+<div class="codehilite"><pre><span class="n">ssh</span> <span class="sr"><apache-id></span><span class="nv">@people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span>
+<span class="n">cd</span> <span class="sr">/www/i</span><span class="n">ncubator</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span>
+<span class="n">svn</span> <span class="n">update</span>
+</pre></div>
+
+
+<p>Due to caching your changes may not be evident immediately on the public website.</p>
</div>
<div id="footera">