[...] > > * We create the additional new list while keeping the old one. The new > > list is for the communication with the kernel developers. > > > > Opinions ? > > I think that having two lists would be a hassle and a mistake. To > have two lists at one host might work, but one list at VGER and > another somewhere else could be counter-productive, as "internal" > communication would be constantly forwarded to the kernel list, and > relevant kernel traffic would have to be forwarded back to the > "internal" list. Think about that for a second. Eventually, we would > probably just drop one list. > > If one list is O(n), then two lists are O(n^2) for anyone who needs > both. I vote for one list, no matter where it's hosted. Don't understand the calculation as I would prefer + instead of * here, but this isn't the point (and if you would do program a bad matching algorithm here it is still O(M*N) ). Don't think that two lists are good without a good topic split. I see a reason for -devel, -users and -announcements list in some projects, but not for a list for "kernel people" and for "other people".
> commercial solution (EMWD):
> - spam filtering
> - open-mesh.net
> - small price < US$20/month
>
> open source host (VGER, freelists.org)
> - spam filtering
> - their-domain.com
> - no price
> - we get added to their project directory, so potential contributors see
> us
Haven't followed the whole discussion, but is it real such a big problem to
change the mailing list address? OK, it shouldn't be done every week, but this
is done for a good reason. Just do an announcement on this list and create an
auto reply (smtp failure notice with further information) when someone writes
to the old list.
Maybe more interesting is the fact that if we can import old information into
the new list. I think mailman stores everything in simple mboxes, or am I
wrong?
And also interesting if we can do backups of the data on vger and co.
Best regards,
Sven
signature.asc
Description: This is a digitally signed message part.
