[Systers-dev] GSoC Bug Fixes and Mailman setup in Ubuntu 9.10

[Jennifer Redman]

On Mon, Mar 29, 2010 at 4:55 AM, kanika vats <kanika.krikan at gmail.com>wrote:

>
> > Migration from regular mailman mailing lists to dlists would be *very*
> > important for any existing project who wanted to use them.  I believe
> > GNOME's lists have many thousand users per list, and hundreds of lists --
> > migrating to newly created lists could be very irritating and even a
> > show-stopper to using the dlists feature.
>

+1




> >
> > Educated speculation on my part: I think many larger projects would make
> > use of the dlists feature if it were available and migration were easy.
> >  Enough that it might be possible to champion it as a feature to add to
> > Mailman 3.  If we were to go that route, we would need to have a
> migration
> > path for enabling dlists on regular lists, and we might also wish to have
> a
> > path for disabling dlists if the list owner no longer wanted them.  That
> > might be getting ahead of ourselves, but it's something to keep in mind.
> >
>
> I have few questions:
>
> 1)When or in what circumstances will a list owner want to disable Dlist
> feature of a dlist enabled list ?
>

This is a good question to answer by writing a few use cases.  We have a
mentor this summer - Sherri Montgomery who is an expert in writing use cases
and doing requirements gathering.


>
> 2)I have heard that Mailman 3 will also be using Database and Storm in
> place
> of  pickle files,exactly for what purpose,I still have to find out.
>
> Has Mailman 3 included this feature of migrating the regular lists of old
> Mailman (using pickle files) to use database?
>

This is a good question to ask on the Mailman-developers list.


>
> If yes then maybe the way they have implemented the migration part may give
> us a good hint of how to handle messages that are send to regular lists
> ,how
> to make the regular lists to use a database updated with info of all the
> threads and messages in the list archives after migration.Besides the hint
> part it will become important to us to make this migration feature
> available
> while working on to integrate the dlist feature with Mailman 3.
>

+1


>
> If no then probably we can concentrate on integrating the existing Dlist
> feature to Mailman3(as Mailman people are themselves thinking Mailman3 to
> be
> used in case of new installations).
> In that case our web interface option whether to create a list as a Dlist
> or
> not is sufficient for the administrator to decide whether he/she wants the
> dlist feature or not.
>

It seems like timing is important here - but I wouldn't think that MM 3.0 is
going to be ready for widespread adoption in the next 6 months. I think it
is probably a good idea, regardless to create a script that migrates current
mailman lists to dlist-enabled lists.


>
> Ans yes migrating the regular lists to dlists is very imporatant wishlist
> item,if we  plan that other organizations like Mozilla/Gnome etc use our
> Dlist feature.
>

+1

 Jen