launchpad-dev team mailing list archive

[Jonathan Lange <jml@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Aug 7, 2009 at 4:20 PM, Maris Fogels wrote:
> On 09-08-05 04:44 PM, Jonathan Lange wrote:
>>
>> On Wed, Aug 5, 2009 at 9:40 PM, Karl Fogel
>> wrote:
>>>
>>> Danilo Šegan  writes:
>>>>
>>>>  * Many Ubuntu-related mailing list requests, which should instead live
>>>> on lists.ubuntu.com
>>>
>>> What if we
>>>
>>>  a) Put a big notice there reminding people to create Ubuntu lists at
>>>    lists.ubuntu.com, and
>>>
>>>  b) If a list has ubuntu in its name, interpose a warning+confirmation
>>>    screen, and
>>>
>>>  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.
>>
>
> So, if I wanted to fix mailing lists, so they no longer need approval, what
> steps must I follow to do so?
>

I can think of three options for a)

  - Adding an "Are you sure?" page as part of the mailing list
creation process. Put the Ubuntu notice there.
  - Adding the Ubuntu notice to the team page just above the "Create a
mailing list" link.
  - Have a create mailing list form that has mostly what's on the
configure mailing list page, except that it also has the Ubuntu
notice.

I don't think b) is necessary -- our implementation of c) will give us
data to determine if it is.

Step c) requires a little bit more hacking, since there's no way of
listing mailing lists on Launchpad that I can find. I would suggest:
  - write up a query that returns the mailing lists created since
yesterday and have running that & examining the output be a part of
the CHR duties.
  - asap changing the +mailinglists page to return a batched list of
mailing lists sorted by date. Since it's an admin-only page, it can
afford to be a little ugly.

And, of course, there's implicit step d), which is disable the approval code.

So, if we really wanted to live on the edge, we could just do step d)
and rely on running a query manually to get us the reports. It's ugly,
but I'd guess it's easily something we could do this cycle.

jml
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.8)

iQEcBAEBCAAGBQJKfFDnAAoJEKoj7DwqcnmXcaYH/jAmE0ffgvTcy2iQaENkvK8U
FB5vKrvOCidP2P7SkhZ4RNrO5VPGr3Dksv9rY6rdO1+WmLdBxHuHkrDvVtxlY1uP
GH6C/Zfi9Ydc7F2qHU5tGgul+eqb/FjrAZpyXroAq9LoliNhgpIXpQN6P3C58Npb
eQdgRxSBOhr5JuDxhOAhq9fUR1q15ZTl0/P4HUNd2Potw6gL3uT+ic5wo4gFTFh+
sT99cIS60OSAX1p7ohW18lwaWZSPip9fGFEC74Id8vuBLlwkvpnncnb6rwp8NNbt
FzQ7oP+IZA3AqC2+AOrnMmgTBKFX8uLzBx0Vqa/nm5G+Bzhge0i4Ylfq758qPPY=
=b42f
-----END PGP SIGNATURE-----