You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by bu...@apache.org on 2017/01/07 15:48:02 UTC
svn commit: r1004377 - in /websites/staging/incubator/trunk/content: ./
guides/website.html report-next-month.html sitemap.html
Author: buildbot
Date: Sat Jan 7 15:48:02 2017
New Revision: 1004377
Log:
Staging update by buildbot for incubator
Modified:
websites/staging/incubator/trunk/content/ (props changed)
websites/staging/incubator/trunk/content/guides/website.html
websites/staging/incubator/trunk/content/report-next-month.html
websites/staging/incubator/trunk/content/sitemap.html
Propchange: websites/staging/incubator/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan 7 15:48:02 2017
@@ -1 +1 @@
-1777811
+1777813
Modified: websites/staging/incubator/trunk/content/guides/website.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/website.html (original)
+++ websites/staging/incubator/trunk/content/guides/website.html Sat Jan 7 15:48:02 2017
@@ -109,53 +109,47 @@
<h2 id='Overview+of+the+Incubator+site'><img src="../images/redarrow.gif" />Overview of the Incubator site</h2>
<div class="section-content">
<p>The Incubator website is generated by the Apache CMS, but it
- is still using the Anakia-based page generation mechanism that was
- used before,
- triggered by a <a href="https://svn.apache.org/repos/asf/incubator/public/trunk/build_cms.sh">CMS external build script</a>.
- </p>
+ is still using the Anakia-based page generation mechanism that was
+ used before,
+ triggered by a <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/build_cms.sh">CMS external build script</a>.
+ </p>
<p>
- This means that you can edit the content either directly in svn
- (and use ant to generate and check the results), or edit via the
- CMS interface, but final publishing has to be done via the CMS
- (see below for how).
- </p>
+ This means that you can edit the content either directly in svn
+ (and use ant to generate and check the results), or edit via the
+ CMS interface, but final publishing has to be done via the CMS
+ (see below for how).
+ </p>
<p>The source to the Incubator website lives at:</p>
<div class="note">
<note><a href="https://svn.apache.org/repos/asf/incubator/public/trunk">
- https://svn.apache.org/repos/asf/incubator/public/trunk</a></note>
+ https://svn.apache.org/repos/asf/incubator/public/trunk</a></note>
</div>
-<p>The production documents are kept in the "infra" SVN repository
- at https://svn.apache.org/repos/infra/websites/production/incubator.
- That directory is then managed by svnpubsub on the server
- to re-create the live website.</p>
+<p>The incubator website is built using <a href="https://cms.apache.org">CMS</a>. After changes are made,
+ you must publish the website.</p>
</div>
<h2 id='Edit+the+content'><img src="../images/redarrow.gif" />Edit the content</h2>
<div class="section-content">
<h3 id='Help+Wanted'>Help Wanted!</h3>
<div class="section-content">
<p>
- People with commit access to the "incubator" SVN can edit the source
- documents in the "content" directory. That is any ASF Member and
- any committer on a current podling in incubation. So you can all help to
- keep your project's Status page up-to-date, and if you find problems with
- the "guidelines" docs then can immediately fix them.
- If unsure, then discuss changes on the general mailing list.
- Note that the "policy" documents need special treatment.
- </p>
+ People with commit access to the "incubator" SVN can edit the source
+ documents in the "content" directory. That is any ASF Member and
+ any committer on a current podling in incubation. So you can all help to
+ keep your project's Status page up-to-date, and if you find problems with
+ the "guidelines" docs then can immediately fix them.
+ If unsure, then discuss changes on the general mailing list.
+ Note that the "policy" documents need special treatment.
+ </p>
<p>
- Anyone else can send patches to those documents to the INCUBATOR issue tracker.
- </p>
+ Anyone else can send patches to those documents to the INCUBATOR issue tracker.
+ </p>
</div>
<h3 id='Checkout+the+Incubator+SVN'>Checkout the Incubator SVN site</h3>
<div class="section-content">
<code>
-svn co https://svn.apache.org/repos/asf/incubator/public/trunk incubator<br />
-cd incubator
-</code>
-<div class="note">
-<note>If you are a committer and intending to commit your changes,
- please ensure you use https instead of http.</note>
-</div>
+ svn co https://svn.apache.org/repos/asf/incubator/public/trunk incubator<br />
+ cd incubator
+ </code>
</div>
<h3 id='Edit+the+source+documents'>Edit the source documents</h3>
<div class="section-content">
@@ -165,100 +159,44 @@ cd incubator
<div class="section-content">
<p>Add new documents in the content directories, then do 'svn add'.</p>
</div>
-<h3 id='Edit+your+project+status+page'>Edit your project status page</h3>
-<div class="section-content">
-<p>The sources for the status pages are in
- <code>content/projects/*.xml</code></p>
-<h4 id='create-status-page'>Create Status Page</h4>
-<div class="section-content">
-<ol>
- <li>
- Copy from the template
- <code>content/projects/incubation-status-template.xml</code> to
- <code>content/projects/${project}.xml</code> then <code>'svn add'</code>
- </li>
- <li>
- The copied template contains customization instructions. Follow them.
- </li>
- <li>
- Go through the template actions. Delete any which are not
- relevant and mark as completed any actions which are already
- done.
- </li>
- <li>
- Add an entry with status "current" to the podlings summary file at
- <code>content/podlings.xml</code> and ensure that the
- list of mentors is up-to-date.
- </li>
- <li>
- Do <code>'svn update'</code> to be sure you are up-to-date.
- </li>
- <li>
- Regenerate the documentation by running <code>'ant'</code> or <code>'build'</code> from the top-level.
- See more detail about this process in the following section. Note that
- there will be many output changes because a new entry has been added to
- the right-hand menu which is replicated on every page. The results wil
- be built to the <pre>target/site</pre> directory by default- please look them over,
- but do not add this directory nor its contents to svn!
- </li>
- <li>
- <code>svn commit</code> all of the source changes with a good message.
- </li>
- <li>
- Review your changes via the
- "<a href="lists.html#cvs+at+incubator.apache.org">commits</a>"
- mail list.
- </li>
- <li>
- Wait a minute or two for the CMS to build your changes, then publish them
- by visiting the <a href="https://cms.apache.org/incubator/publish">Publish site</a>
- page.
- See other <a href="http://www.apache.org/dev/project-site.html">notes</a>
- about this step.
- </li>
- </ol>
-<div class="note">
-<note>This status page is to be kept up to date regularly. This is NOT the same as the 'status report' which is a
- board report entry in the incubator wiki. You still need to follow your monthly/quarterly status reports
- </note>
-</div>
-</div>
-</div>
</div>
<h2 id='Generating+the+top-level+website'><img src="../images/redarrow.gif" />Generating the top-level website</h2>
<div class="section-content">
<div class="note">
<note>Please generate the website yourself and check in the changes.
- If you have any problems, ask for help on the Incubator's
- <a href="lists.html#general+at+incubator.apache.org">general</a> list.</note>
+ If you have any problems, ask for help on the Incubator's
+ <a href="lists.html#general+at+incubator.apache.org">general</a> list.</note>
</div>
<p>In the top-level "incubator" SVN directory, do 'ant'
- to render the HTML files into the <pre>target/site</pre> directory.
- (If you don't have ant installed, you can run build.sh or build.bat
- instead.) If the site built without errors, then do the usual
- SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'.</p>
+ to render the HTML files into the <pre>target/site</pre> directory.
+ You should review those changes before committing.
+ (If you don't have ant installed, you can run build.sh or build.bat
+ instead.) If the site built without errors, then do the usual
+ SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'.</p>
<p>
- Review your changes via the
- "<a href="lists.html#cvs+at+incubator.apache.org">commits</a>"
- mail list.
- </p>
+ Review your changes via the
+ "<a href="lists.html#cvs+at+incubator.apache.org">commits</a>"
+ mailing list. This list will also have buildbot output from running
+ staging builds of the website. If you want to view your changes, you can go to
+ <a href="http://incubator.staging.apache.org">incubator.staging.apache.org</a>.
+ </p>
<p>To update the website, visit <a href="https://cms.apache.org/incubator/publish">Publish site</a>
- and fill out the form. Don't forget to give the CMS build system time to build your changes!
- The CMS provides a page for following the build process.
- </p>
+ and fill out the form. Don't forget to give the CMS build system time to build your changes!
+ The CMS provides a page for following the build process.
+ </p>
</div>
<h2 id='other'><img src="../images/redarrow.gif" />Other notes</h2>
<div class="section-content">
<p>Make sure that your subversion client is properly
- <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.</p>
+ <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.</p>
<p>See other notes for maintenance of
- <a href="http://www.apache.org/dev/project-site.html">apache.org project websites</a>.</p>
+ <a href="http://www.apache.org/dev/project-site.html">apache.org project websites</a>.</p>
<p>
- If you are still having trouble committing, then perhaps the Subversion
- authorization is not yet properly
- <a href="mentor.html#Set+Up+Repository">configured</a>
- to enable your group's access.
- </p>
+ If you are still having trouble committing, then perhaps the Subversion
+ authorization is not yet properly
+ <a href="mentor.html#Set+Up+Repository">configured</a>
+ to enable your group's access.
+ </p>
</div>
</div>
</div>
Modified: websites/staging/incubator/trunk/content/report-next-month.html
==============================================================================
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Sat Jan 7 15:48:02 2017
@@ -67,7 +67,7 @@
<h1>
<a href="http://incubator.apache.org">Apache Incubator</a> Podlings needing to prepare report for February</h1>
<div style="text-align:right;">
-<i>Generated on 2017-01-07T15:45:08Z</i>
+<i>Generated on 2017-01-07T15:47:51Z</i>
</div>
<nav>
<ul>
Modified: websites/staging/incubator/trunk/content/sitemap.html
==============================================================================
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Sat Jan 7 15:48:02 2017
@@ -1275,14 +1275,6 @@ Site map of <a href="http://incubator.ap
<li>
<a href="guides/website.html#Add+a+new+document">Add a new document</a>
</li>
-<li>
-<a href="guides/website.html#Edit+your+project+status+page">Edit your project status page</a>
-<ul>
-<li>
-<a href="guides/website.html#create-status-page">Create Status Page</a>
-</li>
-</ul>
-</li>
</ul>
</li>
<li>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org