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

[Barry Warsaw]

On Aug 1, 2018, at 12:41, Mariatta Wijaya <mariatta.wijaya at gmail.com> 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.

Thanks for writing this up Mariatta.  I think it’s very useful to put stakes in the ground so that these discussions don’t drag on forever.  I agree with those who say that the status quo is an implicit choice of governance models, and I think we shouldn’t operate under implicit rules for too long.  Like Brett, I often have folks coming up to me and asking me what’s going on, and when Python will decide on a governance model.  Let’s not underestimate the message this sends to the outside world.

OTOH, we do have some flexibility in the timeline, and I still believe that we have flexibility in the governance model over the long term.  I’ve no doubt that no matter what we choose, the debate will continue, with ebbs and flows as situations arise.  That may even lead to new (or adjusted) governance models in the future, and that’s fine!  Unlike with Python itself, we aren’t bound to strict backward compatibility. :)

That said, I think it’s worthwhile capturing the proposed governance models in PEPs so that we all know exactly what we’re debating.  October 1st for that round of PEP submissions is quite reasonable IMHO.  Procedurally, I suggest we segregate governance model PEPs in their own 4th digit namespace (e.g. like the way Python 3k started at the 3000s).  8 seems like a good number; we reserve the lower 8ks for “special” PEPs (the problem statement, the choice, the voting procedure, etc.).

We can be a little more loose on the voting schedule, but like Brett, I would like to have a decision by the end of 2018, even if that decision is an explicit choice of status quo.

Cheers,
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180803/d01105f4/attachment-0001.sig>