...
Q. Where will this domain actually "live" and who will manage access?
A. User facing web site will reside at http://incubator.apache.org/openofficeorg/www/ . Current www.openoffice.org will redirect to http://incubator.apache.org/openofficeorg/www/.
Q. How will this sites be accessed/updated?
A. Web site will require commit status and svn access.
...
Q. 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?
A. The new site will use the Apache CMS and Django style headers used by the CMS. All django style templates and programming are stored in the "templates" folder. See http://www.apache.org/dev/cms.html and http://www.apache.org/dev/cmsref.html and local instructions [ http://incubator.apache.org/openofficeorg/website-local.html | http://incubator.apache.org/openofficeorg/website-local.html ].
Q.Can existing content can be ported over?
A.yes.
Q. And if so, how and who will do it?
A. Existing web content MUST be ported over using svn by Apache committers. Anyone can do this but appropriate discussion is mandatory. It might be wise to designate specific areas to certain individuals.
...
Q. Where will this domain actually "live" and who will manage access?
A. Main portion of development web site will reside at http://incubator.apache.org/openofficeorg/ . URL openoffice.apache.org will redirect to http://incubator.apache.org/openofficeorg/.
Q. How will this sites be accessed/updated?
A. Web site will require commit status and svn access.
Q. What to do about "non-product development" projects?
A. – not available yet –
Q. Should the developer arm take over direct involvement with the "mirrors" and "distribution" projects?
A. – not available yet –
...