I am in favor of a time limit. Yet, October 1 seems a bit too long for the initial governance decision (i.e. how to decide how to decide). My perspective, based on transitions in non-profits and the corporate world, is that the longer an organization let's it draw out then fear, uncertainty, and doubt creep in.
We have PEP 10 in place for a strawperson vote. It seems as good as anything to use to determine how to make a decision. Perhaps set a 30 day deadline to submit decision process recommendations. Then take a strawperson poll on each and at the core sprint create a time window for specific proposals on structure be submitted before October 1. My concern if we leave how to decide until at least Oct 1 that the likelihood of completing this year is fairly low. On Wed, Jul 18, 2018, 9:15 PM Mariatta Wijaya <[email protected]> wrote: > +1 > > > On Wed, Jul 18, 2018, 8:54 PM Ethan Furman <[email protected]> wrote: > >> On 07/18/2018 08:45 PM, Łukasz Langa wrote:> >> >> On Jul 18, 2018, at 9:36 PM, Nathaniel Smith <[email protected]> wrote: >> >> >> >> I propose: no governance decisions finalized before October >> >> 1, 2018. >> > >> > +1 but it's okay and expected that discussions here will continue in >> the interim. >> >> Absolutely! Without continuing discussion we'll have nothing to vote on >> come October! ;-) >> >> -- >> ~Ethan~ >> >> _______________________________________________ >> python-committers mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > _______________________________________________ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
