Time to split the mailing list?

[Thomas Arendsen Hein]

* TK Soh <teekaysoh at gmail.com> [20060507 19:46]:
> On 5/6/06, Bryan O'Sullivan <bos at serpentine.com> wrote:
> >If this split is to take place, the obvious choice (to me, anyway) is to
> >move to three lists:
> >
> >      * mercurial-announce - release announcements only
> >      * mercurial-devel - for code-related discussions
> >      * mercurial-users - for Mercurial users
> >
> >What do people think of the idea?
> 
> I personal don't care much about "mercurial-announce" list, since any
> anouncement will most likely make it to other lists anyway, which in
> turn impair it's usefulness.

I'm on a few -annouce lists where I'm very interested in using a
program, but have no time to follow the users or devel discussion.

> Also, when the split does happen, I hope there will be a quick and
> easy way to subscribe to all the list in one transaction, or better
> still, to multiple email addresses. IMO, it's really a hassle having
> to do it once for each list. Especially when you have a few email
> accounts to manage.

Mailman has the concepts of umbrella lists and of topics, maybe this
can be used here. About topics mailman says:

"The topic filter categorizes each incoming email message according
 to regular expression filters you specify below. If the message's
 Subject: or Keywords: header contains a match against a topic
 filter, the message is logically placed into a topic bucket. Each
 user can then choose to only receive messages from the mailing list
 for a particular topic bucket (or buckets). Any message not
 categorized in a topic bucket registered with the user is not
 delivered to the list.

 Note that this feature only works with regular delivery, not digest
 delivery.

 The body of the message can also be optionally scanned for Subject:
 and Keywords: headers, as specified by the topics_bodylines_limit
 configuration variable."

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/