Hi Thanks Richard for taking this up. This was also discussed during the last IRC meeting. See http://meetbot.debian.net/debconf-team/2012/debconf-team.2012-08-13-17.55.log.html#l-181
Martin Zobel-Helas showed some interest to work on this too. Richard Darst <[email protected]> writes: > Hi, > > A discussion on #debconf-team about using lurker as the mailing list > archive turned into a discussion about using lists.debian.org for our > mailing lists. formorer offered to help migrate debconf lists to > there. I've heard this idea mentioned from a debian+debconf and > minimizing redundancy, but it hasn't yet progressed this far. > formorer offered to import all our archives given mboxes. I would keep the old archives to not break links in mails and the wiki. > > Chief among advantages are a significant reduction of workload on our > admin team, with only a minor cost to debian listmasters. Hopefully > there will be fewer of the "lists are down" events, more > standardization for volunteers coming to/from Debian, debian spam > filtering, whitelisting, ..., and non-lurker archives is only a small > side-benefit from this. While I like the lurker interface better than the lists.debian.org archive the other points seem like hughe improvements. Especially better spam handling, sharing infrastructure and a msgid search. So I'm in favour of this. > > For debconf-team: see > http://www.debian.org/MailingLists/HOWTO_start_list > This lists a lot of questions about making lists and the options. > > Listmasters: > our current lists are here: http://lists.debconf.org/mailman/listinfo > Also, we could import debconfNN-localteam lists from DC7--DC11 or so > that aren't listed there. > > Would we use the debconf- prefix? That would be fine for me. Eg. [email protected] > > > Some considerations I can think of: > > - transferring subscribers. I assume we should do this. +1 > > - moderated lists: mainly debconf-announce. formorer offered > shared-secret vs keyring based. I think keyring based would be very > nice. I'm not sure if keyring based is really the best option as this means that someone has to manage this keyring which creates another bottleneck. Shared-secret would be less secure but easier to handle (anyone already having the secret could share it). Is there a way to have a moderation queue like in Mailman? With this everyone could send mails, but only a few could actually make them go out to the list subscribers. > - would we want to redirect mails sent to old list to new list, or > vice versa? only lists.debconf.org -> lists.debian.org redirection seems necessary to me. > > - delegation of management: can management for all lists be easily > given to debconf people, or should is it per-list? Delegation would > reduce listmaster load. What kind of management are you thinking of? List creation or other tasks. I don't think lists.debian.org need any management beside list creation. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ _______________________________________________ Debconf-team mailing list [email protected] http://lists.debconf.org/mailman/listinfo/debconf-team
