I would add that the list is under the PSF CoC and infractions will result in banishment. And I'm not sure if you mailed Nick and I the password for the list -- on the train -- but don't forget that; done that myself. :) I've subscribed Nick, Brett, and Jessica to this list to start out. Jessica: Nick and Brett and I (as well as some other people) had a conversation at the sprints about where it would be appropriate to conduct the conversation about improving the workflow and workflow infrastructure, and we decided we really needed a new list for it. Tracker-discuss was the obvious candidate, but that lists gets all of the tickets and ticket traffic posted on the meta-tracker, and this discussion doesn't need to be interrupted by those, nor will our discussion be limited to topics concerning the tracker. Thus this list. All: Take a look at the list description, and let me know if you think that covers it, and any tweaks you think we should make to that mission statement. First question: should the list be public/open subscription? I don't see any reason it should be closed, but I'm open to opinions :) Assuming it is open subscription, I propose I make an announcement on the python-committers, python-dev, tracker-discuss, and python-mentorship mailing lists inviting interested parties to sign up. --David _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow