That is the exact list that Oracle agreed to transfer to the ASF. If
there are other domains that are related to openoffice.org content, do
we need to check with an Oracle contact to see if they were missed by
mistake or something?
Note that in terms of domain registration, we presumably only need the
TLDs transferred with registrars, and any subdomains we can have
infrastructure organize appropriately.
Or am I missing something?
- Shane
On 8/17/2011 9:01 PM, Kazunari Hirano wrote:
Hi Shane,
Do you have a full list which has http://ja.openoffice.org ?
:)
I would like to see the full list of openoffice.org domains transferred to ASF.
Thanks,
khirano
On Thu, Aug 18, 2011 at 3:55 AM, Shane Curcuru<[email protected]> wrote:
Dear PPMC: please note that a few days ago Oracle and the ASF signed the
legal agreement to transfer ownership of a variety of ooo related domain
names to the ASF. Yay!
Along with the other great work on moving content, you need to work with
infrastructure@ to ensure that the actual domain name registration ownership
is transferred to the Apache infrastructure team - at least, for any domain
names that the podling definitely wants to continue using.
The list of domains includes:
http://openoffice.org
http://testopenoffice.org
http://openoffice2009.com
http://openoffice-gratuit.com
http://openoffice-pt.com
http://openoffice-pl.com
http://openoffice-nl.com
http://openoffice-fr.com
http://openoffice09fr.com
http://de-openoffice.org
http://deopenoffice.org
http://www-open-office.org
http://wwwopen-office.org
http://de-openoffice.com
http://deopenoffice.com
http://es-openoffice.com
http://esopenoffice.com
http://fr-openoffice.com
http://fropenoffice.com
http://it-openoffice.com
http://itopenoffice.com
http://en-openoffice.org
http://enopenoffice.org
http://es-openoffice.org
http://esopenoffice.org
http://fr-openoffice.org
http://it-openoffice.org
http://itopenoffice.org
http://nl-openoffice.org
http://nlopenoffice.org
http://openoffice.org.il
http://itopenoffice.org
Reminder: Apache projects normally host all their content on a *.apache.org
domain. I believe that in ooo's case, the future project will want to host
some content on other, non-a.o domains; however we should strive to make
most of the project be on an Apache site.
- Shane
