You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2003/04/28 23:23:30 UTC

Cocoon Mailinglists

Speaking of transitioning to top level project... What's the status of 
mailing lists migration?

Vadim


Stefano Mazzocchi wrote:

> Pier Fumagalli wrote:
>
>> "Torsten Curdt" <tc...@dff.st> wrote:
>>
>>> What has to be planed/done to make this happen?
>>
>>
>>
>> First of all decide the mailing list names. I propose the following:
>>
>> cocoon-dev@xml.apache.org ->   dev@cocoon.apache.org
>> cocoon-cvs@xml.apache.org ->   cvs@cocoon.apache.org
>> cocoon-doc@xml.apache.org ->   doc@cocoon.apache.org
>> cocoon-users@xml.apache.org -> users@cocoon.apache.org
>>
>> There are few initial stages:
>>
>> 1) (pier) move mailing lists to new hostname:
>>    - this will involve moving the actual directories on the server, the
>>      mailing list downtime will be of approximately 15 to 30 minutes
>>    2) (pier) create aliases for old mailing list "post" address:
>>    - make sure that messages to (for example) 
>> "cocoon-dev@xml.apache.org"
>>      are transparently forwarded to "dev@cocoon.apache.org"
>>    - but at the same time an informative message saying "the mailing 
>> list
>>      has moved, your message has been delievered but remember to use 
>> the new
>>      address in the future" is delievered to the sender
>>
>> 3) (volunteers???) update the documentation and the live site to reflect
>>    changes in the new subscription/unsubscription addresses.
>>
>> Then as soon as this is completed:
>>
>> 4) (pier/dlr) make sure that the archives on eyebrowse reflect this 
>> change.
>>
>> After (I'd say) 15 days, then
>>
>> 5) (pier) not allow transparent forwarding of emails from the old "post"
>>    address to the "new" post address, but simply bounce them 
>> mentioning the
>>    new address.
>>
>> After (I'd say) another 30 days
>>
>> 6) (pier) remove the old email aliases all together.
>>
>> So, if we have a volunteer to update the site, and we all agree, we can
>> start straight away.
>
>
> What about non-ASF mail archives? I think we should tell them we are 
> moving as well so that they can update their stuff.
>
> I'm thinking about MARC and mail-archive
>
> other than this (and Nicola's suggestion) I think it's a nice and sane 
> plan of action.
>
> Stefano.