On Sat, Sep 29, 2018 at 06:53:58PM +1000, Nick Coghlan wrote:
On Sat., 29 Sep. 2018, 11:19 am Barry Warsaw, barry@python.org wrote:
I’m all for supporting the next generation of developers, but not necessarily at the expense of *decades* of established workflow for current developers. Moving to Discourse breaks this and proliferates browser tab syndrome. It’s an experiment worth conducting, but I do think it’s a bit cavalier to shut down python-committers without further discussion.
Especially on the eve of critical governance discussions that will heavily impact the future of python-dev.
Indeed.
This is exactly the kind of arbitrary decision making by an insufficiently representative group that led to us banning making any binding decisions at language summits: their in-person nature means that they're inherently exclusive environments that lead to requirements being overlooked and decisions being made without involving most of the people affected.
I'm surprised how decisions are made on summits as well.
It's quite telling that already 6 core devs, most of whom have contributed huge amounts of code, apparently have not been at that exclusive summit and have indicated that they are uncomfortable with that decision.
Stefan Krah