Governance proposal: Steering Committee and Teams #17
Conversation
|
@jorisvandenbossche here is the first PR for the governance document, covering the front and back matter. |
|
Also see #18 for the material that goes in the middle. |
jorisvandenbossche
changed the title
|
cc @pandas-dev/pandas-core |
|
Thanks for all the work on this @Dr-Irv - looks great to me. |
| slate for an election that will occur by November 15 of that year. For each year after | ||
| the initial election, the current Steering Committee members plus any new volunteers on | ||
| the slate will be elected via approval voting, with the top 5 candidates elected as | ||
| Steering Committee members for the subsequent year. |
There was a problem hiding this comment.
How long do we wait for a "unanimous" vote? Historically I think people just kind of fade away from the project. By the letter this might put us in a spot where someone goes into inactive and the rest of the team has to remove them before making further decisions
There was a problem hiding this comment.
With one year terms, and getting a commitment in October that someone is willing to serve on the Steering Committee in the following year, we're at minimal risk here. It would be odd for someone to say on October 15 "Yes, I'll continue on the steering committee for the next year" and then become inactive pretty quickly. Having said that, if it should occur, there is less than a year until the next election, so the position can be filled.
Maybe you're referring to the Teams identifying by unanimous vote how to remove someone from a Team?
There was a problem hiding this comment.
Yea sorry - this comment should have been in the Teams section. Let me restart it down there for better visibility
|
|
||
| Each Team has defined responsibilities for different aspects of the project. As a | ||
| general rule, an Individual Contributor can be nominated by a member of a Team to become | ||
| a member of that Team, and the Team must unanimously agree to admitting that person to |
There was a problem hiding this comment.
I think requiring unanimous here could be problematic if someone already on the team steps away from the project or is unable to vote for whatever reason. I think we should have a 2 week-1 month timeframe for a team member to object, otherwise any non-votes are not counted
These are changes to the governance documents with respect to the beginning and end of the document, and with the details about the Steering Committee and the concept of Teams. The exact list of teams and their responsibilities are in #18
Summary
We are proposing the following changes to the governance model, based on ideas used in other projects:
To manage the project, there are different Teams that each have responsibility for
specific aspects of the project. Collectively, the members of all Teams are referred to
as Stewards of the project.
Compared to the current governance docs, this removes the notion of a BDFL, and the "Core team" (the current set of committers) essentially becomes the initial Core Library Team (with the same responsibilities and rights as the current core team).