Considering the people involved and the nature of the list, I suspect that adding a new @python.org mailing list would be better than discourse. In my experience, it's very difficult to just follow a single topic on the discourse, and most people complain that the e-mail integration is not great. For something like, "Here's a head's up about something affecting distributors", I don't think Discourse offers much in the way of advantages.
My guess is that distributors would be happiest with a relatively low-volume e-mail list that would point to discussions happening elsewhere (or that announces changes relevant to distributors). Best, Paul On 11/28/20 3:13 PM, Brett Cannon wrote: > So that's two people. If five people involved in the distribution of > Python speak up I will go ahead and create a category on > discuss.python.org <http://discuss.python.org> (people can ask sooner, > but my personal threshold here to do the work myself is 5 😄). > > On Wed., Nov. 25, 2020, 00:18 Petr Viktorin, <encu...@gmail.com > <mailto:encu...@gmail.com>> wrote: > > On 11/24/20 7:50 PM, Brett Cannon wrote: > > If enough people were interested we could create a "Distributors" > > category on discuss.python.org <http://discuss.python.org> > <http://discuss.python.org>. > > I'd join :) > > > > > On Tue, Nov 24, 2020 at 9:08 AM Tianon Gravi > <admwig...@gmail.com <mailto:admwig...@gmail.com> > > <mailto:admwig...@gmail.com <mailto:admwig...@gmail.com>>> wrote: > > > > > I'd love to have an easy way to keep them in the loop. > > > > I'm one of the maintainers on > > https://github.com/docker-library/python > > <https://github.com/docker-library/python> > > (which is what results in https://hub.docker.com/_/python > > <https://hub.docker.com/_/python>), and I'd > > love to have an easy way to keep myself in the loop too! O:) > > > > Is there a lower-frequency mailing list where things like > this are > > normally posted that I could follow? > > (I don't want to be a burden, although we'd certainly really > love to > > have more upstream collaboration on that repo -- we do our > best to > > represent upstream as correctly/accurately as possible, but > we're not > > experts!) > > > > > would it make sense to add a packaging section to our > > documentation or > > > to write an informational PEP? > > > > FWIW, I love the idea of an explicit "packaging" section in > the docs > > (or a PEP), but I've maintained that for other projects > before and > > know it's not always easy or obvious. :) > > > > ♥, > > - Tianon > > 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 > > > > PS. thanks doko for giving me a link to this thread! :D > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > <mailto:python-dev@python.org> > To unsubscribe send an email to python-dev-le...@python.org > <mailto:python-dev-le...@python.org> > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > > https://mail.python.org/archives/list/python-dev@python.org/message/66HPNHT576JKSFOQXJTCACX5JRNERMWV/ > Code of Conduct: http://python.org/psf/codeofconduct/ > > > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/STBTZ6V525QBCCNRTIOVYXPXBB7Z3CE4/ > Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Y3GTLEJIVLA7G4SPD3LEDWMPC7ZISHVS/ Code of Conduct: http://python.org/psf/codeofconduct/
