- 28 Oct 2014
Attendees, you will be considered present in this virtual meeting if you enter your vote in the table below. If you have no opinion on the change, enter "present" or "here".
The SAT met on 2014-10-21 and decided to recommend the following proposal:
The proposal for the suite of public lists would be:
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 firstname.lastname@example.org (for apps), or even email@example.com (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) firstname.lastname@example.org, 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.
The SAT recommended at its meeting on 2014-09-21 that Mario's proposal for data-announce, data-users, and data-devel be adopted. In addition, the SAT recommends that smaller groups be encouraged to set up their own mailing lists, ideally via self-service at lsst.org.
The TCT will now:
Robyn's opinion on the impact upon cost and schedule of accepting each of these changes to the mail lists is that there would be minimal impact.
In principle, I have no objection, but I am worried a bit about the sheer number of emails and different addresses.
|Frossie Economou||Don't care what we call it as long as I can email "my" developers, to which I offer such unstinting support.||Yes|
|Kian-Tat Lim||dm- is not ideal, but it is short and descriptive, and I like it better than data-.||Yes|
|Robert Lupton||I prefer the dm- prefix (we're not discussing data). I don't see the problem with having more lists (more emails, yes!)||Yes|
|Simon Krughoff||+1 for the dm- prefix.||Yes|
|Xiuqin Wu||I prefer dm- prefix too.||Yes|
|Tally of votes:||Quorum is 6 members present. 7 voted affirmatively for the naming change; 4 no-shows. A preference for the 'dm-' prefix over the 'data-' prefix.|