I agree a name other than BDFL should be chosen, especially since (as
I understand it) Guido is still BDFL but just taking a permanent
vacation, and the name implies there should only be one.
Also, if we're considering particular people, I think Nick should also
be considered.
Should the position
On Wed, Jul 18, 2018 at 11:17 AM Tim Peters wrote:
>
>
> [Barry Warsaw]
>>
>> ...
>>
>> * We retain a singular BDFL to lead Python
>> * A Council is selected to serve as advisors to the BDFL, a selection
>> committee for succession, and a check against the BDFL.
>
>
+1 to this idea including Bret
[Barry Warsaw]
> ...
>
* We retain a singular BDFL to lead Python
> * A Council is selected to serve as advisors to the BDFL, a selection
> committee for succession, and a check against the BDFL.
>
You made a fine case for that a single dictator is the best possible
approach, for much the same re
On Tue, Jul 17, 2018 at 7:02 PM, Barry Warsaw wrote:
>
> If you’ve read this far - thank you! Now for the big reveal. I think the
> Next BDFL should be… (drum roll)…
>
> Brett Cannon
>
> To summarize:
>
> * We retain a singular BDFL to lead Python
> * A Council is selected to serve as advisors
I apologize if this has already been mentioned on a different thread,
but something else I like about the BDFL model is that it avoids
"design by committee." I think Python owes a lot of its success to its
coherence as a language, which is in large part due to Guido's vision,
as well as making the
Barry, you offer truly compelling arguments for a new BDFL as GvR's
successor -- FWIW, you've convinced me.
And Brett would be an absolutely outstanding pick as that "new BDFL" -- on
this, I need no convincing.
Alex
On Tue, Jul 17, 2018 at 7:08 PM Barry Warsaw wrote:
> I’d like to propose an
I wholeheartedly agree with Barry's suggestion.
It offers a single person who can communicate the design vision. While the
support of a council will help spread out the work and provides a great way
to grow future leaders and a smooth transition if for any reason (family,
work, health, etc.) the n
On Jul 17, 2018, at 22:15, Eric V. Smith wrote:
> On 7/17/2018 10:02 PM, Barry Warsaw wrote:
>> I’d like to propose an alternative model, and with it a succession plan,
>> that IMHO hasn’t gotten enough discussion. It’s fairly radical in that it
>> proposes to not actually change that much!
>>
On 7/17/2018 10:02 PM, Barry Warsaw wrote:
I’d like to propose an alternative model, and with it a succession plan, that
IMHO hasn’t gotten enough discussion. It’s fairly radical in that it proposes
to not actually change that much!
TL;DR: I propose keeping a singular BDFL and adding a Counci
I’d like to propose an alternative model, and with it a succession plan, that
IMHO hasn’t gotten enough discussion. It’s fairly radical in that it proposes
to not actually change that much!
TL;DR: I propose keeping a singular BDFL and adding a Council of Advisors that
helps the BDFL in various
Excerpts from Jack Jansen's message of 2018-07-17 11:33:22 +0200:
>
> > On 17 Jul 2018, at 02:02, Tim Peters wrote:
> >
> > [Tim]
> >> Guido's most visible (well, to us committers) BDFL role has been in
> >> "yes/no", "go/nogo" language/library design questions, which don't even
> >> overlap w
> On 17 Jul 2018, at 02:02, Tim Peters wrote:
>
> [Tim]
>> Guido's most visible (well, to us committers) BDFL role has been in
>> "yes/no", "go/nogo" language/library design questions, which don't even
>> overlap with the PSF's proper concerns.
>>
>> But I'm not sure it's fully appreciated ju
Le 17/07/2018 à 04:07, Brett Cannon a écrit :
>
> This ties into the core dev sponsor idea that got floated where all
> inexperienced PEP authors need someone to sign up to shepherd them
> through the process. That way everything is more structured and, with
> this idea, also more uniform.
This
13 matches
Mail list logo
