4 ms·

> 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 re

> 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?

mjw1007 8y ago
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.
zrail 8y ago
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.
hannasanarion 8y ago
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.
porpoisely 8y ago
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?
- mcherm 8y ago
  > Do you know if council members can be re-elected? Yes, they can, and likely will be in many cases.
  - porpoisely 8y ago
    Thanks, that's what I figured. So the vote would be a formality most of the time and not something revolutionary.
    - fesoliveira 8y ago
      Well, it creates a way for other members of the core team to replace someone they disagree with without having to call for a no-confidence vote all the time. I don't know what you mean by "revolutionary", but the point of these kinds of councils is to uphold the vision and principles of the language, and so long as the people in the council are making the correct calls in those regards, there would be no reason to replace them.
- zapzupnz 8y ago
  Because in any discussion about "new councils" ever, it never means that the entire council would be different. Be it a parliament, city council, a church committee, or a software project — the point isn't who is in it or for how long but rather that an election (or any other sort of opportunity for rearrangement) has been held. "New council", in this circumstance, is shorthand for "holding an election for the council".
ubernostrum 8y ago
This was borrowed straight from Django's process; our technical board gets re-elected every release cycle. It's a pretty low-traffic and low-turnover group in Django. I've done it four releases in a row, for example. When there's only one feature release in most years, it's not an issue at all to do a quick call for volunteers. In Django's case, often there's not a real need for an "election" since you only get as many volunteers as there are spots on the technical board.

> 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?

mjw1007 8y ago

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.

zrail 8y ago

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.

hannasanarion 8y ago

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.

porpoisely 8y ago

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?

mcherm 8y ago
> Do you know if council members can be re-elected? Yes, they can, and likely will be in many cases.
- porpoisely 8y ago
  Thanks, that's what I figured. So the vote would be a formality most of the time and not something revolutionary.
  - fesoliveira 8y ago
    Well, it creates a way for other members of the core team to replace someone they disagree with without having to call for a no-confidence vote all the time. I don't know what you mean by "revolutionary", but the point of these kinds of councils is to uphold the vision and principles of the language, and so long as the people in the council are making the correct calls in those regards, there would be no reason to replace them.
zapzupnz 8y ago
Because in any discussion about "new councils" ever, it never means that the entire council would be different. Be it a parliament, city council, a church committee, or a software project — the point isn't who is in it or for how long but rather that an election (or any other sort of opportunity for rearrangement) has been held. "New council", in this circumstance, is shorthand for "holding an election for the council".

ubernostrum 8y ago

This was borrowed straight from Django's process; our technical board gets re-elected every release cycle. It's a pretty low-traffic and low-turnover group in Django. I've done it four releases in a row, for example. When there's only one feature release in most years, it's not an issue at all to do a quick call for volunteers. In Django's case, often there's not a real need for an "election" since you only get as many volunteers as there are spots on the technical board.