Frossie Economou, Joshua Hoblitt and I had some further discussion today and converged to the following proposal (very similar to the one above):
- firstname.lastname@example.org: a mailing list for public (e.g., release) announcements
- email@example.com: the list for users of DM software (it was felt that eschewing a mailing list for SO or CQ may be too radical)
- firstname.lastname@example.org: general development-related discussions (there will always be a need to reach all developers; e.g., the recent discussions on github-JIRA integration/notifications would go here)
An alternative prefix may be 'dm-', if there's pushback that 'data-' is too broad. Another option (that just occurred to me and isn't necessarily supported by either Frossie or Josh) is 'code-'. All these lists would be public, archived, and open to anyone to subscribe.
In addition to these, we would let any of the working groups (or subgroups) open mailing lists as necessary. So, for example, we could have email@example.com (for apps), or even firstname.lastname@example.org (if algo-devel becomes unwieldy and needs further splitting), etc. We'll rely on common sense to not let the number of lists grow to >= number of people in DM. These lists could be private, if necessary, but the default should be to make them public.
Finally there'd be a (private) email@example.com, for broadcasts to DM staff only.
We'd ask Iain to create these lists.
Once they are created, the proposal is to retire and archive lsst-data and lsst-dm-stack-users lists after some grace period (~1 week).
The subscribers to lsst-data would be alerted to re-subscribe to either the -announce, -users, or -devel lists. The subscribers to lsst-dm-stack-users will be alerted to the name change, re-subscribed to data-users (or, if Mailman allows for that, lsst-dm-stack-users would just be renamed to data-users), and an alias will be set up to forward e-mails from lsst-dm-stack-users to data-users.