Re: moving projects to beaver

On Apr 24, 2004, at 9:08 AM, Mauro Talevi wrote:
> Also, even creating the new top-level projects,
> I assume we are keeping jcontainer as an incubator/discussion project.
> If so what will be the mappings for the new jcontainer lists:
>
> jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org -> dev-+bEyFkcr8cOBX3rNsQtK8+b9Vox/[email protected]
> or perhaps better
> jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org -> user-+bEyFkcr8cOBX3rNsQtK8+b9Vox/[email protected] 
> ?
>
> jcontainer-commits-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org -> scm-+bEyFkcr8cOBX3rNsQtK8+b9Vox/[email protected]
>
> I assume that at least initially the jcontainer lists will be 
> forwarded to the new ones, is that right?
>
> if you port the subscription list, the gmane mapping should be kept as 
> is (gmane is simply a client to the subscription list).

Yea, splitting the projects means we need to figure out what to do with 
the lists.

We currently have 2 lists, jcontainer-interest and jcontainer-commits. 
If we split out DNA and Loom, each will have dev/user/scm ...

The mapping you have above is fine w/me, I guess we will leave it up to 
individuals to subscribe to the new lists?
-pete