OK, the apache.org account is live, and we are go for the migration... So I want to ask here before I do anything, about exactly what strategy we should take. So I have the following questions:
1) Should we take this opportunity to start making major changes before we actually go "live" with a web site on xml.apache.org, so that we can make a decent splash? Things I'm talking about are wholesale module renames, remove CharsetConv in favour of plain Text::Iconv or Encode.pm, fix Makefile.PL once and for all, move AxKit.pm to lib/, where it would be more sensible to keep it, etc. Or should we just move everything there, and fix things gradually, after all, time is of the essence. 2) How should we migrate the web site over? Apache.org has a very specific set of style guides (which cocoon doesn't use, so we could migrate the site as-is, or even make it a redirector to axkit.org), which would mean changing our XML files into their format. That's not difficult I'm sure. But it would need doing by somebody. 3) Migrating the mailing lists. I see three options here: a) make axkit-users and axkit-devel redirect to the equivalent lists on apache.org. b) migrate all the users over en-masse c) leave everything - let people re-subscribe at apache.org, after all, there may be lots of people who would like to fall off the list at this time. Thanks for your time. There are probably other issues, so if you have questions, don't be afraid to ask. -- <!-- Matt --> <:->Get a smart net</:-> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
