Please extend the deadline: next week, I will be at EuroPython (I don't think that I will have time to sit down and come up with something), and I'm (more or less) in holiday the whole month of August.
Victor 2018-07-19 21:43 GMT+02:00 Antoine Pitrou <anto...@python.org>: > > Le 19/07/2018 à 21:35, Carol Willing a écrit : >>> >>>>> My biggest concern is that dragging this on into the new year will >>>>> result in more bikeshedding, more uncertainty, and less confidence in >>>>> the developer community decision making ability. >>>> >>>> That's a fair point. But there's also an opposite concern that >>>> discussions may be deterred or cut short by a too tight deadline. Even >>>> simple and uncontentious PEPs take time to write, discuss and finalize. >>> >>> Maybe it would be better to focus on a first date for submitting >>> proposals and then wait to set the rest of the deadlines until after >>> we have a bit more of the discussion behind us. That will give us >>> a sense for how much consensus there is and how much more discussion >>> might be needed. >> >> This suggestion seems to balance well the different perspectives. >> >> Proposals due by Sept 9, 2018 AOE. > > I still think it's too short. Imagine someone leaving in August. > Besides catching up with work, the beginning of a new school year (if > they have kids) and other things, they have only 9 days to contribute > usefully. > > This is not something we can mobilize for to try and compress the time > span as much possible. > > Regards > > Antoine. > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/