DOC: Add governance document draft - #163
Conversation
|
@f-brinkmann @sikersten @ahms5 , Could you please check if there's something I forgot here? |
mberz
changed the title
| ### What Reaches the Steering Council | ||
|
|
||
| In practice, most decisions in the pyfar project will be resolved by Maintainers via lazy consensus or informal vote. | ||
| **The committee is involved when:** |
There was a problem hiding this comment.
| **The committee is involved when:** | |
| **The council is involved when:** |
| In practice, most decisions in the pyfar project will be resolved by Maintainers via lazy consensus or informal vote. | ||
| **The committee is involved when:** | ||
|
|
||
| - A DEP has **cross-package or project-wide impact** — for example, introducing a new shared data structure, changing a convention adopted by all packages, or deprecating functionality that other packages depend on |
There was a problem hiding this comment.
changing a convention adopted by all packages
How should we treat the template package in this context? It has been used in the past to establish such conventions.
| **The committee is involved when:** | ||
|
|
||
| - A DEP has **cross-package or project-wide impact** — for example, introducing a new shared data structure, changing a convention adopted by all packages, or deprecating functionality that other packages depend on | ||
| - A DEP proposes a **large new feature or new package** — meaning functionality that significantly expands a package or the project, requires substantial development effort, or has broad implications for the user-facing API |
There was a problem hiding this comment.
A DEP proposes a large new feature or new package
Not sure about this point, since we have not fully defined DEPs yet. Is there any DEP that does not need to be discussed by the council? If not, I would suggest writing here that every DEP needs approval by the council. The explanations for what a DEP does can then be implemented by linking to DEP0.
| - A DEP has **cross-package or project-wide impact** — for example, introducing a new shared data structure, changing a convention adopted by all packages, or deprecating functionality that other packages depend on | ||
| - A DEP proposes a **large new feature or new package** — meaning functionality that significantly expands a package or the project, requires substantial development effort, or has broad implications for the user-facing API | ||
| - A question of **removing or significantly altering** long-standing functionality that many users rely on | ||
| - A DEP proposes a **governance change** — modifying roles, voting rules, the DEP process, or the Code of Conduct |
There was a problem hiding this comment.
See comment above. If we agree that every DEP needs approcal by the council, this is point is just and obsolete explanation of what DEPs are for.
| - Maintainers across packages **cannot reach consensus** after discussion | ||
| - A decision has legal, financial, or external relations implications | ||
|
|
||
| ### Composition |
There was a problem hiding this comment.
Should we add a point, what is required to change the rules for this composition? A DEP?
| - Organizing and preparing Steering Council meetings | ||
| - Ensuring the composition of the Steering Council stays current | ||
|
|
||
| ### Selection Process |
There was a problem hiding this comment.
We should add a point at which point in time the selections happen and who is deciding that. Is it a special meeting, how is it announced?
|
|
||
| ### Stepping Down & Emeritus Status | ||
|
|
||
| Members who step down from the Steering Council are recognized with **emeritus status**, acknowledging their past contributions. Emeritus members may attend meetings and contribute to discussions but do not hold voting rights. |
There was a problem hiding this comment.
| Members who step down from the Steering Council are recognized with **emeritus status**, acknowledging their past contributions. Emeritus members may attend meetings and contribute to discussions but do not hold voting rights. | |
| Members who step down from the Steering Council are recognized with **emeritus status**, acknowledging their past contributions. Emeritus members may attend meetings and contribute to discussions but do not hold the rights of an active council member. |
To remove confusion with the voting as part of the selection process
|
|
||
| ### Expected Conduct | ||
|
|
||
| Steering Council members are expected to participate in votes, particularly on major DEPs and governance decisions. If a member becomes inactive in the project for a period of 6 months, they will be considered for removal from the Council. Before removal, inactive Member will be approached to see if they plan on returning to active participation. If not, they will be removed immediately upon a Council vote. |
There was a problem hiding this comment.
I would suggest to add giving them the option to step down as an alternative to simply removing them, such that they reach the emeritus status.
| ### Expected Conduct | ||
|
|
||
| Steering Council members are expected to participate in votes, particularly on major DEPs and governance decisions. If a member becomes inactive in the project for a period of 6 months, they will be considered for removal from the Council. Before removal, inactive Member will be approached to see if they plan on returning to active participation. If not, they will be removed immediately upon a Council vote. | ||
| Sustained absence from votes without notice may prompt a discussion about whether a member wishes to continue in the role. |
There was a problem hiding this comment.
Can you clarify what you mean with this point? Present in the council meeting but not voting, or not being present in the council meetings?
github-project-automation
Bot
moved this from Drafting Phase
to Require review
in Weekly Planning
2 participants
Proposed Changes
This draft was used as basis for the establishment of pyfar's first steering council.
Note: The use of markdown is only temporary and will be changed before the PR is finalized.