Discussions about the design and implementation of the main apache.org website are held on the site-dev@ apache.org mailing list.
The top level ASF-wide apache.org website is managed as described at http://www.apache.org/dev/infra-site.html
- Note that this does not include project-specific websites (which each manage their own content), nor does it include any of the wikis used at the ASF.
- The infrastructure team and any ASF member has write access to the source code for the apache.org website. Read access is public.
- The body (Latest News, etc.) is located at xdocs/index.xml
- The right hand side navigation is located at xdocs/stylesheets/project.xml
- The body and the right hand side navigation seem to be aggregated by the ant build file (build.xml)
- Jun-2010: the most recent X number of entries are pulled in as links to the apache.org/index.xml page by the Ant build script.
The project list on the right hand side should be dynamically included (from http://projects.apache.org/) [SebastianBazley: why projects? Is that the canonical list of TLPs? Surely there is a better source?][ShaneCurcuru: The list should be pulled in from whatever the best canonical source is. Long-term, that source should be projects.a.o once it's complete]
News entries should be shared with the ASF Feather Blog (http://blogs.apache.org/foundation/)
- One should be able to select different search results providers (e.g. Google, bing, "Lucene/Nutch")
- What is your backwards compatibility policy?
- What is your forwards compatibility policy?
- Static export of the content
- Can also be edited/published using SVN
- What is your license? (What happens if the license is changed?)
- What about support?
- What about putting the code into escrow?
- What if company who owns the code is dissolved or sold to another company?
- How can a third-party developer enhance/customize proprietary components?
- What if project/organization is dissolved?
Confluence (according to Luciano is already powering http://community.apache.org/)