(In reply to comment #9)
>> Not sure this is relevant as this extension isn't really user-facing, but if
>> you want to find someone to review the design, go for it.
> 
> Well, for some definition of user, right? It has sysop user facing UI. For a
> design review, the Design mailing list is a good place to start (and then
> ping until success).

Lego: please go ahead and e-mail the design mailing list (include a working demo of the tool, of course). If they have constructive feedback, wonderful. Otherwise, I don't consider this a blocker to deployment.

>> Greg: how do we get this extension reviewed for architecture/performance and
>> security?
> 
> First pass would be to send a note to wikitech-l asking for help.
> Unfortunately, this week is a combined Tech Days and All Hands so WMF tech
> staff will be slower to respond than normal, but I know you know who to ping
> as needed (Aaron/Tim for arch, Chris for security).

Lego: please go ahead and e-mail wikitech-l asking for a review once you're ready and you've done your best to ensure that the extension is in a reviewable state. Test rigorously!

If you could cross-reference these two mailing list posts on this bug, that would be wonderful.

> Well, if there are any userfacing bits (even for non-mortals), then it'd be
> good to have a walk-through of how the extension is supposed to work/what the
> process is. Think of it as a required bit of user documentation :)

If you write docs about how to create one of these mythical screencasts, I'll consider it. In the meantime, over a decade of development has progressed without these being a requirement. We're not going to start with this extension. :-)

>>> Community support: no?
>> 
>> Yes, plenty of it.
> 
> Awesome. I believe you, but would appreciate links to where discussion has
> happened.

This request is a blocker to bug 35306. It falls outside the requirement for community consensus as it's an obvious and uncontroversial enhancement request; it is replacing a non-production, largely unsupported tool (i.e., the Python script that currently powers [[m:Global message delivery]]); and it has limited exposure (only admins will have access by default, and even most admins won't use this tool... for now).

Bug 35306 gives most of the background here, but it's probably reasonable for me to point out that many (if not most) global message deliveries are connected to Wikimedia Foundation staff. The targets lists at [[m:Global message delivery/Targets]] comprise hundreds (maybe thousands) of users who have signed up for various newsletters and other mailings, in addition to a number of distribution lists used by Wikimedia volunteers and staff (including technical announcements and other breaking changes announced to [[m:Distribution list/Global message delivery]]). You could consider this a third or fourth exemption to the community consensus guideline, if you'd like. ;-)