...
- Primary restructuring based on "users" vs "developers"
- User focused areas would remain on a server designated as: openoffice.org
- Native-language areas would remain with the "language".openoffice.org specification
- Developer areas would be assigned to: openoffice.apache.org.
Public/User Site ("new" openoffice.org)
Setup Issues
- Where will this domain actually "live" and who will manage access?
- How will this site be accessed/updated: svn vs wiki vs ?
...
- Once a new "site" is determined, what content tools (cms, standard headers/footers, server-side include templates, etc.) are available and who can access them?
- What will be contained on the initial structure/landing page do we want for this site?
- Can existing content can be ported over? And if so, how and who will do it?
- A flexible content management system must be available for this site outside the Apache "committer" process if at all possible.
Project/Developer Site (openoffice.apache.org)
-- to be continued --
Other Sites/Services (especially OO.o wiki and extensions)
...