[python-committers] Reminder of BDFL succession timeline + CFP

M.-A. Lemburg mal at egenix.com
Wed Aug 1 17:10:17 EDT 2018

Thanks for your action plan, Mariatta, but I'm -1 on having
strict timelines for these processes.

We need to gradually approach a new model as we've done in the
past decades and not push for any possibly borked model right from
the start. The processes for this need to stay flexible, easy
to adapt and include the possibility for failure.

There is no rush for any such model. There is no need to select
anyone for life or longer periods: e.g. we may want to change the
whole model after 2 years - what are we then going to do with
those persons ?

We may very well end up not having any kind of governance body
initially and use a simple democratic voting scheme for any
issues which may arise.

FWIW, I don't see anyone in the core development team with the
necessary language design skills, vision or intuition to provide
an overarching scheme for the future of Python and I don't expect
that we'll find such people any time soon.

What we do have is a good number of smart people with expert
domain knowledge. We should build on those for the time being
until we have grown a vision for the future to provide more

So let's ponder some more about ideas we could use to
get there and perhaps watch some Monty Python movies for
inspiration ;-)

Marc-Andre Lemburg

On 01.08.2018 21:41, Mariatta Wijaya wrote:
> Since this is like a CFP I figured we should clarify what's expected the
> proposal, and I also wanted to be more detailed in the timeline.
> *Oct 1 00:00:00 UTC:* Deadline of coming up with proposals of governance
> model.
> To be included in the proposal:
> - explanation and reasoning of the governance model
> - expected roles and responsibilities
> - candidate for the role need not be included at this time, since we're
> only choosing the governance model. Depending on the governance model
> chosen, we might have different people to be nominated. There will be a
> separate process for nominating the candidate.
> - the term of governance: is it for life? 5 years? 10 years?
> Who can submit the proposal?
> Python core developers. Individual core devs can submit a proposal, or
> co-author the proposal with another core dev.
> How to submit the proposal?
> Proposal should be in a form of a PEP, and merged into peps repo before Oct
> 1 00:00:00 UTC. Proposals not merged after Oct 1 00:00:00 UTC will not be
> considered.
> *Oct 1 - Nov 15: Review period.*
> All core developers will review the PEPs, and ask any questions to the PEP
> author. This timeline allows for enough time for all core devs to carefully
> review each PEPs, and for authors to respond.
> There will be two parts of this:
> *Review phase 1: Oct 1- Nov 1:* Allow changes and tweaks to the proposed
> PEPs.
> I figured people will have questions and will need to clarify the PEPs
> during this period. But if we want the PEP to be final by Oct 1, that's
> fine by me. maybe allow typo fixes still.
> *Review phase 2: Nov 1 00:00:00 UTC*: No more changes to the above PEPs.
> No more tweaks to these PEPs. PRs to these PEPs should be rejected.
> This is the final chance to carefully review all governance PEPs, and
> formulate your decisions.
> *Nov 15 00:00:00 UTC: Voting for new governance model starts, and will go
> for 2 weeks*
> Send reminders for folks to vote.
> Who can vote:
> Only core developers can vote.
> *Vote will be anonymous.*
> *We will use the system used to elect PSF board members.*
> *Dec 1 00:00:00 UTC: Voting ended*.
> The most voted proposal will be accepted.
> Depending on the chosen governance model, we'll begin nominating candidates
> to fill the role(s).
> *Dec 10 00:00:00 UTC Deadline for nominating candidates to fill the role*
> Maybe just one PEP to list all the nominations, instead of separate PEPs of
> each candidates.
> Who can nominate: Python core developers
> Who can be nominated: Python core developers
> *Dec 15 00:00:00 UTC Voting for new successor starts*
> (Depends on the governance model chosen on Dec 1)
> *Who can vote:*
> *Only core developers can vote.*
> *Vote will be anonymous.*
> *We will use the system used to elect PSF board members.*
> *Jan 1 00:00:00 UTC Voting for new successor ends.* Most voted candidate(s)
> is chosen.
> The PSF's Code of Conduct applies to all interactions with core devs
> regarding this process, including interactions in any mailing lists, zulip,
> IRC, twitter, GitHub, backchannels.
> Questions
> 1. For the purpose of eligibility (for voting or writing the PEP), who are
> considered as "core developers"? Anyone in python-committers? Anyone on
> Python Core GitHub team? Anyone with commit bit? What about core developers
> of alternate implementation (PyPy, IronPython, etc)
> 2. Are people ok UTC timezone?
> 3. Should this be a PEP?
> Mariatta
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/

Marc-Andre Lemburg

Professional Python Services directly from the Experts (#1, Aug 01 2018)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the python-committers mailing list