incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1004380 - in /websites/staging/incubator/trunk/content: ./ guides/sites.html report-next-month.html sitemap.html
Date Sat, 07 Jan 2017 15:52:38 GMT
Author: buildbot
Date: Sat Jan  7 15:52:38 2017
New Revision: 1004380

Log:
Staging update by buildbot for incubator

Modified:
    websites/staging/incubator/trunk/content/   (props changed)
    websites/staging/incubator/trunk/content/guides/sites.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:52:38 2017
@@ -1 +1 @@
-1777813
+1777815

Modified: websites/staging/incubator/trunk/content/guides/sites.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/sites.html (original)
+++ websites/staging/incubator/trunk/content/guides/sites.html Sat Jan  7 15:52:38 2017
@@ -23,7 +23,9 @@
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   <link rel="stylesheet" href="../style/bootstrap-1-3-0-min.css" type="text/css" />
   <link rel="stylesheet" href="../style/style.css" type="text/css" />
-    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml"
href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
+    <link rel="alternate" title="general@incubator.apache.org
+            Archives
+        " type="application/atom+xml" href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom"
/>
     <title>Podling Web Site Guide - Apache Incubator</title>
   
  </head>
@@ -109,166 +111,162 @@
             <h2><img src="../images/redarrow.gif" />Abstract</h2>
 <div class="section-content">
 <p>
-Podlings need to build a community in Apache in order to be accepted
-as part of the Apache Software Foundation. One of the tools used to build
-a community is the web site.
-        </p>
+                Podlings need to build a community in Apache in order to be accepted
+                as part of the Apache Software Foundation. One of the tools used to build
+                a community is the web site.
+            </p>
 </div>
         <h2><img src="../images/redarrow.gif" />Podling Website Requirements</h2>
 <div class="section-content">
 <p>
-Podlings are, by definition, not yet fully accepted as part of the
-Apache Software Foundation. Therefore, they are subject to additional
-constraints on their websites.  These policies MUST be adhered to
-before Graduation is considered unless prior approval is obtained from
-the Incubator PMC.
-        </p>
+                Podlings are, by definition, not yet fully accepted as part of the
+                Apache Software Foundation. Therefore, they are subject to additional
+                constraints on their websites. These policies MUST be adhered to
+                before Graduation is considered unless prior approval is obtained from
+                the Incubator PMC.
+            </p>
 <ul>
-            <li>
-The published site for each podling must conform to the guidelines in
-<a href="../guides/branding.html">Podling Branding/Publicity</a>.
-            </li>
-            <li>
-The sources for every podling site sources should be maintained in the podling's site SVN
or git directory
-            </li>
-            <li>
-The published site for each podling should conform to this URL space:
-<code>http://podlingname.incubator.apache.org/</code>
-            </li>
-			<li>
-The staging site for each podling should conform to this URL space:
-<code>http://podlingname.staging.apache.org/</code>
-		    </li>
-            <li>
-Every podling should maintain an incubation status file under:
-<code>http://incubator.apache.org/projects/podlingname.html</code>
-            </li>
-            <li>
-Eventual extra incubation documents should be filed under:
-<code>http://incubator.apache.org/projects/podlingname/**</code>
-           </li>
-           <li>
-The website lives in the following directory on people.apache.org:
-           <code>/www/podlingname.apache.org/content/</code>
-           </li>
-        </ul>
+                <li>
+                    The published site for each podling must conform to the guidelines in
+                    <a href="../guides/branding.html">Podling Branding/Publicity</a>.
+                </li>
+                <li>
+                    The sources for every podling site sources should be maintained in the
podling's site SVN or git
+                    directory
+                </li>
+                <li>
+                    The published site for each podling should conform to this URL space:
+                    <code>http://podlingname.incubator.apache.org/</code>
+                </li>
+                <li>
+                    The staging site (if using CMS) for each podling should conform to this
URL space:
+                    <code>http://podlingname.staging.apache.org/</code>
+                </li>
+                <li>
+                    Every podling should maintain an incubation status file under:
+                    <code>http://incubator.apache.org/projects/podlingname.html</code>
+                </li>
+                <li>
+                    Eventual extra incubation documents should be filed under:
+                    <code>http://incubator.apache.org/projects/podlingname/**</code>
+                </li>
+            </ul>
 </div>
         <h2><img src="../images/redarrow.gif" />Creating the Podling Website</h2>
 <div class="section-content">
 <h3>Creating A Good Podling Site</h3>
 <div class="section-content">
 <p>
-  Apache Project Web Sites typically include several standard pages.
-  Each page is formatted with a navigation bar on the left and a project
-  standard header that includes the Incubator graphic.
-            </p>
-<p>
-  The Web Site can be established during incubation, and migrated
-  after incubation to a permanent place in the TLP home.
-            </p>
+                    Apache Project Web Sites typically include several standard pages.
+                    Each page is formatted with a navigation bar on the left and a project
+                    standard header that includes the Incubator graphic.
+                </p>
+<p>
+                    The Web Site can be established during incubation, and migrated
+                    after incubation to a permanent place in the TLP home.
+                </p>
 <ul>
-                <li>
-  Project Home Page: the primary entry point to the site; contains 
-  project description, news, invitation to join the project.
-                </li><li>
-  License Page: usually, the Apache License 2.0
-                </li><li>
-  Downloads: many projects in incubation will release code,
-  and this page describes them and has links to the download pages
-  that redirect to Apache Mirror sites.
-                </li><li>
-  Documentation: this page describes the project documentation,
-  including javadoc for Java projects; guides, tutorials, and links to
-  external documentation.
-                </li><li>
-  Committers: a list of current committers on the project.
-                </li><li>
-  Mailing Lists: there are several mailing lists that the
-  community might be interested in, and this page contains mailto: links
-  that allow easy subscription (and unsubscription) to any of them.
-                </li><li>
-  FAQ: frequently asked questions are answered here.
-                </li><li>
-  Road Map: if the project has a vision of future community
-  or development activities, the road map is published here.
-                </li><li>
-  Source Code: links to the browsable source repository and
-  svn commands to check out the sources.
-                </li><li>
-  Coding Standards: the coding standards for submitted code
-  by the community, along with a description of how strict the project
-  intends to be.
-                </li><li>
-  Issue Tracking: links to the JIRA or other issue tracking
-  tool, possibly including frequently used filters for issue lists.
-                </li><li>
-  Dependencies: other projects that this project depends on.
-                </li><li>
-  favicon: the project's icon in a format suitable for a browser's address bar.  If absent,
an Apache Feather will be displayed.
-                </li></ul>
+                    <li>
+                        Project Home Page: the primary entry point to the site; contains
+                        project description, news, invitation to join the project.
+                    </li>
+                    <li>
+                        License Page: usually, the Apache License 2.0
+                    </li>
+                    <li>
+                        Downloads: many projects in incubation will release code,
+                        and this page describes them and has links to the download pages
+                        that redirect to Apache Mirror sites.
+                    </li>
+                    <li>
+                        Documentation: this page describes the project documentation,
+                        including javadoc for Java projects; guides, tutorials, and links
to
+                        external documentation.
+                    </li>
+                    <li>
+                        Committers: a list of current committers on the project.
+                    </li>
+                    <li>
+                        Mailing Lists: there are several mailing lists that the
+                        community might be interested in, and this page contains mailto:
links
+                        that allow easy subscription (and unsubscription) to any of them.
+                    </li>
+                    <li>
+                        FAQ: frequently asked questions are answered here.
+                    </li>
+                    <li>
+                        Road Map: if the project has a vision of future community
+                        or development activities, the road map is published here.
+                    </li>
+                    <li>
+                        Source Code: links to the browsable source repository and
+                        svn commands to check out the sources.
+                    </li>
+                    <li>
+                        Coding Standards: the coding standards for submitted code
+                        by the community, along with a description of how strict the project
+                        intends to be.
+                    </li>
+                    <li>
+                        Issue Tracking: links to the JIRA or other issue tracking
+                        tool, possibly including frequently used filters for issue lists.
+                    </li>
+                    <li>
+                        Dependencies: other projects that this project depends on.
+                    </li>
+                    <li>
+                        favicon: the project's icon in a format suitable for a browser's
address bar. If absent, an
+                        Apache Feather will be displayed.
+                    </li>
+                </ul>
 </div>
 <h3 id='Tool'>Web Site Generation Tool</h3>
 <div class="section-content">
 <p>
-  The choice of tool used to generate the web site is left to 
-  the podling. If you already have a tool that you are comfortable
-  with, you can continue to use it. If you do not, consider using
-  the <a href="http://www.apache.org/dev/cmsref.html">Apache CMS</a>.
-            </p>
-<p>
-  Regardless of which tool you use, the web site should be maintained
-  in the svn repository, and include the site generation tool as a binary
-  file. This simplifies the process of site generation and enables changes
-  to the site to be made by any committer. The generated site should also
-  be checked into svn. This allows the generated site to be relocated
-  to any part of the Apache site after incubation is complete.
-            </p>
-<p>
-  Since the site is independent of the code, it should exist high in
-  the svn repository, e.g. parallel to the trunk of the source tree.
-            </p>
+                    The choice of tool used to generate the web site is left to
+                    the podling. If you already have a tool that you are comfortable
+                    with, you can continue to use it. If you do not, consider using
+                    the <a href="http://www.apache.org/dev/cmsref.html">Apache CMS</a>.
+                </p>
+<p>
+                    Regardless of which tool you use, the web site should be maintained
+                    in the svn repository, and include the site generation tool as a binary
+                    file. This simplifies the process of site generation and enables changes
+                    to the site to be made by any committer. The generated site should also
+                    be checked into svn. This allows the generated site to be relocated
+                    to any part of the Apache site after incubation is complete.
+                </p>
+<p>
+                    Since the site is independent of the code, it should exist high in
+                    the svn repository, e.g. parallel to the trunk of the source tree.
+                </p>
 </div>
-<h3>Publishing The Website</h3>
+<h3>Publishing Your Website</h3>
 <div class="section-content">
 <p>
-              <b>THIS IS VERY OUTDATED AND NEEDS FIXING</b><br />
-The website is published by checking out the content from SVN into 
-the directory <code>/www/incubator.apache.org/content/podlingname</code>
-(old way) or <code>/www/podlingname.apache.org</code> (new way) on 
-<code>people.apache.org</code>. The particular SVN module used to
-store the website is a matter for the podling but it should be in SVN.
-           </p>
-<p>
-People using Maven, Forrest, or any other tool still have
-to address the SVN publishing requirement that the
-infrastructure team has laid out. If that is done, then we
-just run "svn update" in that directory to load the site from
-SVN.
-           </p>
-<p>
-The Mentors MUST add the information to the podling
-incubation status file, to describe the SVN module and the
-directory which holds the published site.
-           </p>
+                    Managing a podling's website is now the same as a top-level project.
 Review the <a href="http://www.apache.org/dev/project-site.html">Infra Documentation
on Project Websites</a>
+                </p>
 </div>
 <h3 id='create-website-using-wiki'>Using A Wiki To Create Documentation</h3>
 <div class="section-content">
 <p>
-        Podlings may use a wiki to create documentation (including the website) providing
that follow the 
-        <a href="http://cwiki.apache.org/CWIKI/">guidelines</a>. In particular,
care must be taken to 
-        ensure that access to the wiki used to create documentation that may be included
in the project
-        release is restricted to only those with filed <a href="http://www.apache.org/licenses/">individual
CLAs</a>. The PPMC MUST review all changes and ensure that
-        trust is not abused.
-        </p>
+                    Podlings may use a wiki to create documentation (including the website)
providing that follow the
+                    <a href="http://cwiki.apache.org/">guidelines</a>. In particular,
care must be taken to
+                    ensure that access to the wiki used to create documentation that may
be included in the project
+                    release is restricted to only those with filed <a href="http://www.apache.org/licenses/">individual
+                    CLAs</a>. The PPMC MUST review all changes and ensure that
+                    trust is not abused.
+                </p>
 </div>
 </div>
         <h2><img src="../images/redarrow.gif" />Main Incubator Website</h2>
 <div class="section-content">
-<p>Please read the <a href="website.html">Incubator Website guide</a>
-      for more information about how the general Incubator site is laid out
-      and how to edit/regenerate the top-level documentation and a project's
-      status file.
-      </p>
+<p>Please read the
+                <a href="website.html">Incubator Website guide</a>
+                for more information about how the general Incubator site is laid out
+                and how to edit/regenerate the top-level documentation and a project's
+                status file.
+            </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:52:38 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:47:51Z</i>
+<i>Generated on 2017-01-07T15:52:27Z</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:52:38 2017
@@ -1246,7 +1246,7 @@ Site map of <a href="http://incubator.ap
 <li>
 <a href="guides/sites.html#Tool">Web Site Generation Tool</a>
 </li>
-<li>Publishing The Website</li>
+<li>Publishing Your Website</li>
 <li>
 <a href="guides/sites.html#create-website-using-wiki">Using A Wiki To Create Documentation</a>
 </li>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message