Another one is core-mentorship, which satisfies the same criteria; and in my view this has the added and useful property that its beneficiaries are non-core members. After that I'd do core-workflow. Honestly I'd leave python-committers alone for a while, we're a curmudgeonly group. :-)
On Wed, Nov 1, 2017 at 7:54 PM, Barry Warsaw <ba...@python.org> wrote: > On Nov 1, 2017, at 19:42, Guido van Rossum <gu...@python.org> wrote: > > > > Maybe we should try it on some other list too? I know it works "in > principle" and I'd love for all Python mailing lists to migrate, but I'd > like to have some more experience with community mailing lists before > tackling python-dev. > > What about core-workflow or committers? I think some of the criteria are: > > * Gets a fair bit of traffic, but not too much > * Is okay with a little bit of downtime for the migration > * Willing to put up with any transient migration snafus > * Amenable to trying the new UI > * Has the BDFL as a member :) > > -Barry > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > guido%40python.org > > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
