Jack Jansen Jack.Jansen at cwi.nl
Fri Aug 3 05:05:54 EDT 2018

• Previous message (by thread): [python-committers] Reminder of BDFL succession timeline + CFP
• Next message (by thread): [python-committers] Reminder of BDFL succession timeline + CFP
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> On Aug 3, 2018, at 02:19, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> 
> OTOH, it would be great if we can at least set a date to start the
> discussion so that everybody can plan for it and join.  That's the
> only way to keep the discussion open and equally accessible for
> everyone.  If we do nothing, then naturally, those core devs who know
> each other personally will start forming their opinion in isolated
> groups. Many people will feel that they are completely removed from
> the decision process and will end up in a very uncomfortable position.

Hmm, you’re right. Not having any sort of timeline or process will mean that lots of stakeholders will not know about any discussions and feel left out by the end.

Some sort of a schedule would ameliorate that.

Jack

---

• Previous message (by thread): [python-committers] Reminder of BDFL succession timeline + CFP
• Next message (by thread): [python-committers] Reminder of BDFL succession timeline + CFP
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list