On Tue, 19 Jun 2018 at 13:16 Guido van Rossum <gu...@python.org> wrote:
> I'm happy to see you do this. It'll be very interesting what kind of > responses you get. Do you know how to get the list of 130 people? (I don't, > but Mariatta probably has it already.) > WFM! Thanks, Ethan! I guess the first step is to go through https://bugs.python.org/user?iscommitter=1&@action=search&@sort=github&@pagesize=300 and contact the folks missing a GitHub username and to track who says "yes" or "no" in https://devguide.python.org/developers/ in new active/emeritus lists (opened https://github.com/python/devguide/issues/390 to track the list change). After that would be to go through the Python Core team on GitHub -- which should match who has a GitHub username on b.p.o -- and then correlate that with who has committed in the last year on appropriate repos and then reach out to those people. -Brett > On Tue, Jun 19, 2018 at 12:51 PM Ethan Furman <et...@stoneleaf.us> wrote: > >> On 06/19/2018 11:17 AM, Brett Cannon wrote: >> > On Mon, 18 Jun 2018 at 17:56 Guido van Rossum wrote: >> >> >> I'd do it as follows. This basically makes withdrawal voluntary unless >> >> they don't respond at all. >> >> >> >> 1. Make a list of people who've not shown any sign of activity (on the >> >> b.p.o. or GitHub, as reviewer or committer) for at least one year. >> >> >> >> 2. Email all of them, asking if they still want to be a core dev. >> Choices >> >> could include >> >> Â a. Yes >> >> Â b. Keep the logo and b.p.o. access but disable GitHub key >> >> Â c. Drop everything >> >> >> >> 3. If someone doesn't respond despite repeated attempts (maybe using >> >> different email addresses or social media) then after 4 weeks assume >> >> they meant to answer (c). But if they write back later they can be >> >> restored according to their preference (a, b, c), no questions asked. >> > >> > One point I want to make about this pull approach versus a push one is >> this >> > is going to be a lot of work. :) For the "no GitHub username" >> situation on >> > bugs.python.org <http://bugs.python.org> there are 80 people to reach >> out >> > to. For people with commit rights who have not committed in the past >> year >> > to CPython (because that's the best data point I have without writing >> custom >> > code to find out who has commented on a PR recently), that would >> require >> > reaching out to an additional 50 people. So we're looking at >> potentially up >> > to 130 people to try and track down. >> >> I'm happy to do this. >> >> > We can make a complete list as people seem to want that and have it be >> active >> > versus emeritus and list the year people got their commit rights. >> >> > At the end of that month whomever is still listed as emeritus we turn >> off >> > their commit access and b.p.o extras. We announce this here, >> python-dev, >> > social media, etc. IOW this becomes more opt-in/push than opt-out/pull. >> >> The problem with this approach as it's one time -- as soon as someone >> fades away it's once again out of date. >> >> I'll take on the task of contacting the 130 people to get this started, >> then once a year somebody does the same thing >> with whichever handful of people have gone dormant that year. >> >> Sound fair? >> >> -- >> ~Ethan~ >> >> _______________________________________________ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > > > -- > --Guido van Rossum (python.org/~guido) > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/