OOo-to-ASF-site-recommendation

Main (Existing) Web Site (openoffice.org)

Current main navigation areas:

1. why: Why use OpenOffice.org
2. download: Direct download specific product only
3. support: Support area (many alternativis!)
4. extensions: get extensions (housed at OSU)
5. participating: catch-all for all kinds of particiaption
6. news (top navigation bar): news, manually edited
7. download: Complete download page (user, developer version, other information)
8. projects (top navgiation bar): a complete listing of all projects
9. people: registered OO.o participants (needed for mailing list activity, etc.)
10. my page (participant login)
11. about: a page about the project

New Site Recommendations (in discussion)

Overview

1. Primary restructuring based on "users" vs "developers"
2. User focused areas would remain on a server designated as: openoffice.org
3. Native-language areas would remain with the "language".openoffice.org specification
4. Developer areas would be assigned to: openoffice.apache.org.

User Site ("new" openoffice.org)

Setup Issues

1. Where will  this domain actually "live"  and who will manage access?
2. How will this site be accessed/updated: svn vs wiki vs ?

Content Management

1. 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?
2. What will be contained on the  initial structure/landing page do we want for this site?
3. Can existing content can be ported over? And if so, how and who will do it?
4. A flexible content management system must be available for this site outside the Apache "committer" process if at all possible.

Developer Site (openoffice.apache.org)

-- to be continued --

Other Sites/Services (especially OO.o wiki and extensions)

see Transition Planning