On Wednesday, October 3, 2018, Jeroen Demeyer <j.deme...@ugent.be> wrote:
> Hello, > > I would like to propose Petr Viktorin as BDFL-Delegate for PEP 580, titled > "The C call protocol". He has co-authored several PEPs (PEP 394, PEP 489, > PEP 534, PEP 547, PEP 573), several of which involve extension modules. > > Petr has agreed to become BDFL-Delegate for PEP 580 if asked. Also Antoine > Pitrou, INADA Naoki and Nick Coghlan have approved Petr being BDFL-Delegate. > > I am well aware of the current governance issues, but several people have > mentioned that the BDFL-Delegate process can still continue for now. I > created a PR for the peps repository at https://github.com/python/peps > /pull/797 +1. Are we doing upvotes on the mailing list or on the GitHub PR and/or issue now? "[Python-ideas] PEPs: Theory of operation" https://markmail.org/thread/zr4o6l7ivnj4irtp """ Process suggestions that could minimize non-BDFL's BDFL legwork: [...] * Use GitHub reactions for voting on BDFL delegates, PEP final approval, and PEP sub issues? * Specify a voting deadline? * How to make a quorum call? * Add '@core/team' as reviewers for every PEP? * Link to the mailing list thread(s) at the top of the PR * [ ] Add unique message URLs to footers with mailman3 * What type of communications are better suited for mailing lists over PEP pull-requests and PEP code reviews? [The original thread is probably a better place to discuss PEP process going forward] """ > > > Cheers, > Jeroen Demeyer. > _______________________________________________ > 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/wes. > turner%40gmail.com >
_______________________________________________ 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
