launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #00297
Re: How do I fix mailing lists? (was: Re: Why do lists need special approval?)
On Aug 7, 2009, at 11:20 AM, Maris Fogels wrote:
a) Put a big notice there reminding people to create Ubuntu lists at
lists.ubuntu.com, and
This would be easy to add to the ~team/+mailinglist template.
b) If a list has ubuntu in its name, interpose a warning
+confirmation
screen, and
I'm not so sure about imposing an additional page for confirmation,
but we could just disallow such requests unless done by a ~mailing-
list-expert.
Remember that mailing lists take their name from their team, so
probably the best place to put this would be in browser/team.py in
request_list_creation_validator().
c) For the few mistakes that still happen, just do post-facto review
and move them over to ubuntu.com as needed.
+1
a) & c) are really cheap too.
b) would not be so bad either.
So, if I wanted to fix mailing lists, so they no longer need
approval, what steps must I follow to do so?
I think it's a moderate amount of work to change the mailing list
creation workflow, but it may not be that bad. The main thing is that
when a list is requested it goes into the MailingListStatus.REGISTERED
state. From there the global +mailinglists page displays all such
lists and lets the admin approve, discard, etc. the pending mailing
lists.
Once a message is APPROVED, the creation request gets sent to Mailman
and things proceed from there. I think the quick solution would be
that a pre-approved mailing list would go straight to the APPROVED
state, skipping REGISTERED. That might be all you need to fix this,
but there would be follow on work to remove all traces of the
REGISTERED state (except perhaps as a deprecated placeholder in the
enum).
We can either talk about this in more detail if you're interested in
doing the work, or someone can open a bug if they want it badly enough
and I'll work on it.
-Barry
Attachment:
PGP.sig
Description: This is a digitally signed message part
Follow ups
References