Which reminds me. I don’t follow Discourse (or Discord) closely and I missed the start of the nomination period. In the past didn’t we send out email reminders?
Email notifications used to go out to python-committers@python.org until it was archived in favor of discuss.python.org.
The only email notifications that continue are direct outreach to individual core devs that are marked as inactive, and email ballots.
Can we send email in the future? I also missed the starting period, and this seems important enough to warrant an extra notification.
6 Likes
I’m not sure how such an email should be sent, as I previously did until python-committers was archived (before the last SC election), given that there is no mailing list I’m aware of that core devs are expected to be subscribed to and that discuss.python.org appears to be the generally preferred venue for most discussions/announcements.
Couldn’t you just use the voter list? In your first respose you said that email is used to email ballots, so it follows (?) that you have the technology. 
2 Likes
There’s a difference between BCCing 23 folks (some of whom complain that such a BCC is odd/suspicious) and emailing well over 100 core devs from an individual address.
I’m absolutely fine emailing a mailing list or creating topics on a forum, but sending multiple emails to bypass the limits on BCC sending is just a bit too fragile.
I’d suggest that Python core devs establish an expected means for announcements and stick with it.
6 Likes
I’m going to break the discussion on notifications into a new topic to ensure it has space to continue, as this topic the original host topic will be closed tomorrow when voting opens.
1 Like
Current summary of the situation, as I understand it:
Documentation on the Responsibilities of a Core Developer make mention of discuss.python.org replacing much of the older mailing lists, but does not make clear what the expectations/responsibilities of the Core Developers or those who need to reach them are around announcements or critical notifications, nor does the documentation around Following Python’s development.
This seems to have created a schism in expectations of some Core Developers around how and where they will be notified of important things like Steering Council Election cycles, and a gap for people in roles who need to make that contact in knowing what the right method is.
Perhaps we need a python-committers-announce mailing-list?
The difference between Discourse and a ML is that most Discourse users won’t get e-mail notifications on a new Discourse topic. So even though you might check out Discourse on a semi-regular basis, you might still miss an important topic during 3 weeks.
7 Likes