Python gets a new governance model
1–10 of 191 posts
Re: Python gets a new governance model
#2> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected.
Won‘t that get old really soon?
Re: Python gets a new governance model
#3> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected. Won‘t that get old really soon?
I expect in most cases the same people will stand and be re-elected.
One advantage of doing things this way is that it makes it easy for people to step down when they've had enough.
Re: Python gets a new governance model
#4> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected. Won‘t that get old really soon?
Python feature releases are not very frequent. The document notes that the second council (first to serve a full term) will serve for 18 months.
Re: Python gets a new governance model
#5> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected. Won‘t that get old really soon?
It's only every 18 months. It'll probably be mosyly the same people all the time, Guido and Tim Peters could probably hold seats as long as they want them.
Re: Python gets a new governance model
#6Councils, committees, multiple obtuse voting systems, governance documents, 'courts' of appeal... Why are they so keen to construct such a grim bureaucracy for themselves?
Re: Python gets a new governance model
#7> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected. Won‘t that get old really soon?
Do you know if council members can be re-elected? Does "new council" imply a brand new set of council members? If so wouldn't that hurt institutional knowledge?
Re: Python gets a new governance model
#8Councils, committees, multiple obtuse voting systems, governance documents, 'courts' of appeal... Why are they so keen to construct such a grim bureaucracy for themselves?
[deleted]
Re: Python gets a new governance model
#9Councils, committees, multiple obtuse voting systems, governance documents, 'courts' of appeal... Why are they so keen to construct such a grim bureaucracy for themselves?
Zizek is famous for pursuing a line very much against the grain; people intellectually similar to him argue for a society organised informally and locally, like a commune - but he argues that he'd rather be living in a bureaucracy in which he doesn't have to worry about all the smallest decisions and direct democracy. To him, the trouble of the USSR wasn't all the bureaucracy, it was that it wasn't bureaucratic enough to the point where it was easy to game the system.
>Žižek now believes that efficient bureaucracy is the necessary corollary of any successful future state. While often alluding to the utopian impulse that imagines a political community beyond “what is”—including Derrida’s “democracy of the future”—such imagining should not exceed the strictures imposed on the world by technological complexity, sprawling populations and megalopolises. In fact one should be able to take utilities and health services for granted. Freedom of choice should not have to extend to one’s electricity vendor and Internet provider, or even what hospital one wants to convalesce in.[0]
and,
>I think he agrees with Laclau and Mouffe, that every radical solution is temporary, 'lives in borrowed time'. This means that an 'organizational structure' must not become sedimented, but remain open. This probably sounds a bit abstract, but it matters, as it assumes the position opposite of e.g. Stalinism.[1]
On some level I agree with him, as much as it's contrary to the self-organizing semi-anarchist hacker spirit.
[0] https://criticaltheoryresearchnetwork.com/2017/08/10/bureauc...
[1] https://www.reddit.com/r/zizek/comments/6mmtpg/what_kind_of_...
Re: Python gets a new governance model
#10> Steering council members will serve for the length of single Python feature release; after each release, a new council will be elected. Won‘t that get old really soon?
Do you know if council members can be re-elected? Does "new council" imply a brand new set of council members? If so wouldn't that hurt institutional knowledge?
> Do you know if council members can be re-elected?
Yes, they can, and likely will be in many cases.