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.
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.
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.
http://podlingname.incubator.apache.org/
http://podlingname.staging.apache.org/
http://incubator.apache.org/projects/podlingname.html
http://incubator.apache.org/projects/podlingname/**
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.
The Web Site can be established during incubation, and migrated after incubation to a permanent place in the TLP home.
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 Apache CMS.
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.
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.
Managing a podling's website is now the same as a top-level project. Review the Infra Documentation on Project Websites
Podlings may use a wiki to create documentation (including the website) providing that follow the guidelines. 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 individual CLAs. The PPMC MUST review all changes and ensure that trust is not abused.
Please read the Incubator Website guide 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.