From 6e5d871b63ea17bb5699cf80ca017af9c56327bb Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Sat, 7 Oct 2023 12:21:08 +0200 Subject: [PATCH 01/12] add new issue template [skip ci] --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/discussion.md | 25 +++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 1 deletion(-) create mode 100644 .github/ISSUE_TEMPLATE/discussion.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 22234bd7..08658392 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -2,7 +2,7 @@ name: Bug report about: Create a report to help us improve title: '' -labels: '' +labels: 'bug' assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/discussion.md b/.github/ISSUE_TEMPLATE/discussion.md new file mode 100644 index 00000000..6c0a6b09 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/discussion.md @@ -0,0 +1,25 @@ +--- +name: Question, Feature, Documentation +labels: 'question' +about: Ask question, request feature or documentation update +--- + +### Thank you for taking the time to share your thoughts with us. + +We welcome all suggestions for new features or documentation updates +helping others to make better use of this project. + +As with any other topic you'd like to discuss with the community, +we'd primarily like to invite you to [open a discussion](https://github.com/openssl/openssl/discussions) +item with your concern. + +If you have a bug to report please use the [Bug report template](https://github.com/open-quantum-safe/oqs-provider/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=). + +If you have an issue with the project that does not qualify as a bug +and have already explored the code to the extent that you can make a +proposal how to handle the issue, please feel free to open a +"blank issue" providing all information you have already collected. + +Please remember to tell us which code version/branch you are using and +then briefly describe the issue and proposal how to resolve it if +available. From 3b3a90ef22ad8c0bf8b00796409d5ab076ac9952 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Sat, 7 Oct 2023 12:31:54 +0200 Subject: [PATCH 02/12] add CONTRIBUTING policy [skip ci] --- CONTRIBUTING | 57 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 CONTRIBUTING diff --git a/CONTRIBUTING b/CONTRIBUTING new file mode 100644 index 00000000..fc00765d --- /dev/null +++ b/CONTRIBUTING @@ -0,0 +1,57 @@ +# Contributing (policy) + +This file documents the contribution guidelines used for this project. + +## Roles + +The following roles exist in the project: + +1. Maintainer: Person with github administrative rights. + +2. Committer: Person with github "Write" privileges; this entails the right and obligation to review PRs by Contributors and to actively participate in discussions. + +3. Contributor: Person that has contributed code. + +4. Users: Person using the project passively or actively, e.g., by participating in discussions. + +## Relationships between roles + +Any User may also be Contributor. Any Contributor may also be Committer. Any Committer may also be Maintainer. A Maintainer must be a Committer. + +## Change of role + +Any User may become Contributor by creating a pull request (PR) and getting it successfully reviewed and merged by Committers. + +Any Contributor can become Committer by contributing sufficient code and displaying deep subject matter knowledge in discussions such that a majority of Committers vote for this change of role. A Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of Committers. + +As such voting decision may be considered subjective, Contributors striving to become Committers are encouraged to ask for advice by Committers as to what --if anything-- should be done (additionally to already documented knowledge in contributions) to attain this status. Baseline requirements for contributions are documented in [CONTRIBUTING.md](CONTRIBUTING.md). Any Contributor can create a discussion item to request a vote to become Committer. + +Any Committer can become Maintainer by majority vote of voting Committers. A current Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of all Committers. + +A Maintainer is not permitted to remove another Maintainer's github privileges. + +A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. + +## Voting + +Votes are to be executed by way of open github discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. + +Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. If such period extends beyond one year, the Committer permanently loses role and rights. The period is documented in this file next to the person's name below. + +## Documentation of roles + +Current Maintainer(s) and Committer(s) are to be documented below by way of reference to their github handles. + +### Maintainer(s) + +@baentsch + +### Committer(s) + +@baentsch +@levitte +@bhess +@dstebila +@thb-sb +@christianpacquin + From 00c07ed3adda1ba8aea3079417d2ed0c6ca60aec Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Mon, 16 Oct 2023 08:38:17 +0200 Subject: [PATCH 03/12] correct maintainer status [skip ci] --- CONTRIBUTING | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING b/CONTRIBUTING index fc00765d..d0815e1b 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -45,6 +45,7 @@ Current Maintainer(s) and Committer(s) are to be documented below by way of refe ### Maintainer(s) @baentsch +@dstebila ### Committer(s) From 23c9cb91100b4874679246fabb5264db5d102707 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Wed, 18 Oct 2023 08:29:08 +0200 Subject: [PATCH 04/12] feedback by @levitte incorporated [skip ci] --- CONTRIBUTING | 59 +-------------------------------------------------- GOVERNANCE.md | 57 +++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 58 insertions(+), 58 deletions(-) create mode 100644 GOVERNANCE.md diff --git a/CONTRIBUTING b/CONTRIBUTING index d0815e1b..242d7f46 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -1,58 +1 @@ -# Contributing (policy) - -This file documents the contribution guidelines used for this project. - -## Roles - -The following roles exist in the project: - -1. Maintainer: Person with github administrative rights. - -2. Committer: Person with github "Write" privileges; this entails the right and obligation to review PRs by Contributors and to actively participate in discussions. - -3. Contributor: Person that has contributed code. - -4. Users: Person using the project passively or actively, e.g., by participating in discussions. - -## Relationships between roles - -Any User may also be Contributor. Any Contributor may also be Committer. Any Committer may also be Maintainer. A Maintainer must be a Committer. - -## Change of role - -Any User may become Contributor by creating a pull request (PR) and getting it successfully reviewed and merged by Committers. - -Any Contributor can become Committer by contributing sufficient code and displaying deep subject matter knowledge in discussions such that a majority of Committers vote for this change of role. A Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of Committers. - -As such voting decision may be considered subjective, Contributors striving to become Committers are encouraged to ask for advice by Committers as to what --if anything-- should be done (additionally to already documented knowledge in contributions) to attain this status. Baseline requirements for contributions are documented in [CONTRIBUTING.md](CONTRIBUTING.md). Any Contributor can create a discussion item to request a vote to become Committer. - -Any Committer can become Maintainer by majority vote of voting Committers. A current Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of all Committers. - -A Maintainer is not permitted to remove another Maintainer's github privileges. - -A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. - -## Voting - -Votes are to be executed by way of open github discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. - -Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. If such period extends beyond one year, the Committer permanently loses role and rights. The period is documented in this file next to the person's name below. - -## Documentation of roles - -Current Maintainer(s) and Committer(s) are to be documented below by way of reference to their github handles. - -### Maintainer(s) - -@baentsch -@dstebila - -### Committer(s) - -@baentsch -@levitte -@bhess -@dstebila -@thb-sb -@christianpacquin - +For Linux Foundation contract adherence, consider the contents of the file [GOVERNANCE.md](GOVERNANCE.md) instead. diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 00000000..71e1e00e --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,57 @@ +# Contributing (policy) + +This file documents the contribution guidelines used for this project. + +## Roles + +The following roles exist in the project: + +1. Maintainer: Person with github administrative rights. + +2. Committer: Person with github "Write" privileges; this entails the right and obligation to review PRs by Contributors and to actively participate in discussions. + +3. Contributor: Person that has contributed code. + +4. Users: Person using the project passively or actively, e.g., by participating in discussions. + +## Relationships between roles + +Any User may also be Contributor. Any Contributor may also be Committer. Any Committer may also be Maintainer. A Maintainer must be a Committer. + +## Change of role + +Any User may become Contributor by creating a pull request (PR) and getting it successfully reviewed and merged by Committers. + +Any Contributor can become Committer by contributing sufficient code and displaying deep subject matter knowledge in discussions such that a majority of Committers vote for this change of role. A Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of Committers. + +As such voting decision may be considered subjective, Contributors striving to become Committers are encouraged to ask for advice by Committers as to what --if anything-- should be done (additionally to already documented knowledge in contributions) to attain this status. Baseline requirements for contributions are documented in [CONTRIBUTING.md](CONTRIBUTING.md). Any Contributor can create a discussion item to request a vote to become Committer. + +Any Committer can become Maintainer by majority vote of voting Committers. A current Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of all Committers. + +A Maintainer is not permitted to remove another Maintainer's github privileges. + +A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. + +## Voting + +Votes are to be executed by way of open github discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. + +Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. If such period extends beyond one year, the Committer permanently loses role and rights. The period is documented in this file next to the person's name below. + +## Documentation of roles + +Current Maintainer(s) and Committer(s) are to be documented below by way of reference to their github handles. + +### Maintainer(s) + +@baentsch +@dstebila + +### Committer(s) + +@baentsch +@bhess +@dstebila +@thb-sb +@christianpacquin + From c8747c37ced768493f1bd4ee0aeaec5cd0170828 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Wed, 18 Oct 2023 17:36:02 +0200 Subject: [PATCH 05/12] Details in GOVERNANCE.md (#287) The title and explanation aren't right, and what voting includes isn't clear. --- GOVERNANCE.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 71e1e00e..d42f2b15 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,6 +1,6 @@ -# Contributing (policy) +# Governance -This file documents the contribution guidelines used for this project. +This file documents the governance guidelines used for this project. ## Roles @@ -34,6 +34,8 @@ A Committer automatically may be moved to Contributor status if not actively con ## Voting +Change of role or changes to this document is subject to voting. + Votes are to be executed by way of open github discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. If such period extends beyond one year, the Committer permanently loses role and rights. The period is documented in this file next to the person's name below. From 66c0c2531b7e5dd76a503b4b88a1bdf68dd641c2 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Sat, 7 Oct 2023 12:31:54 +0200 Subject: [PATCH 06/12] add CONTRIBUTING policy [skip ci] --- CONTRIBUTING | 1 - 1 file changed, 1 deletion(-) delete mode 100644 CONTRIBUTING diff --git a/CONTRIBUTING b/CONTRIBUTING deleted file mode 100644 index 242d7f46..00000000 --- a/CONTRIBUTING +++ /dev/null @@ -1 +0,0 @@ -For Linux Foundation contract adherence, consider the contents of the file [GOVERNANCE.md](GOVERNANCE.md) instead. From e8787725bd95f26591be7c3b0b51ff7a697d1375 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Wed, 18 Oct 2023 08:29:08 +0200 Subject: [PATCH 07/12] feedback by @levitte incorporated [skip ci] --- GOVERNANCE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index d42f2b15..1afde518 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -56,4 +56,3 @@ Current Maintainer(s) and Committer(s) are to be documented below by way of refe @dstebila @thb-sb @christianpacquin - From 7ff9dd51f00fbe756b1e77eb9ebfa016d4421b00 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Sun, 22 Oct 2023 18:39:47 +0200 Subject: [PATCH 08/12] updates following SustainOSS feedback --- GOVERNANCE.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1afde518..fb8cb6c7 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -30,7 +30,11 @@ Any Committer can become Maintainer by majority vote of voting Committers. A cur A Maintainer is not permitted to remove another Maintainer's github privileges. -A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. +A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status and with this, the Maintainer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. + +Any person violating the [code of conduct](CODE_OF_CONDUCT.md], consistently not fulfilling the role responsibilities or other reasons can lose the role held if a simple majority of Committers votes for such removal and no Maintainer vetos that decision. If a Maintainer is to be removed from that role a 2/3 majority of Committers must agree. + +Depending on the reason for removal, a Maintainer may be converted to Emeritus status. Emeritus Maintainers may still be consulted on some project matters, and can be returned to Maintainer status if their availability changes and a simple majority of Committers agrees. ## Voting From f9f53893d294a466b7af470ec4a0defdcccaad48 Mon Sep 17 00:00:00 2001 From: Spencer Wilson Date: Thu, 26 Oct 2023 00:47:07 -0400 Subject: [PATCH 09/12] Governance document fixes / clarification / softening (#297) * Fix link to OpenSSL * s/github/GitHub/ * Clarify reinstatement into role * English fixup * Add cheesy foreword --- .github/ISSUE_TEMPLATE/discussion.md | 2 +- GOVERNANCE.md | 34 ++++++++++++++++------------ 2 files changed, 20 insertions(+), 16 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/discussion.md b/.github/ISSUE_TEMPLATE/discussion.md index 6c0a6b09..328941c5 100644 --- a/.github/ISSUE_TEMPLATE/discussion.md +++ b/.github/ISSUE_TEMPLATE/discussion.md @@ -10,7 +10,7 @@ We welcome all suggestions for new features or documentation updates helping others to make better use of this project. As with any other topic you'd like to discuss with the community, -we'd primarily like to invite you to [open a discussion](https://github.com/openssl/openssl/discussions) +we'd primarily like to invite you to [open a discussion](https://github.com/open-quantum-safe/oqs-provider/discussions) item with your concern. If you have a bug to report please use the [Bug report template](https://github.com/open-quantum-safe/oqs-provider/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=). diff --git a/GOVERNANCE.md b/GOVERNANCE.md index fb8cb6c7..1579aa72 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,14 +1,18 @@ # Governance -This file documents the governance guidelines used for this project. +## Foreword + +This file documents the governance guidelines used for this project. It is principally concerned with defining the roles of project contributors, the associated rights and responsibilities, and the process for transitioning between them. As such, this document is written in a fairly formal and precise tone, so as to be succint and unambiguous. This should not be interpreted as a lack of warmth on the part of the OQS team---we're really quite friendly! We do not intend to act as gatekeepers by laying out this tier of roles and the associated rules. Instead, we hope that clearly defining these roles and the processes for attaining them shows contributors a clear path by which to become more involved in project governance, if they so wish. We welcome all questions, discussions, and contributions, and we would love to have more people on board. + +We recognize that some of the policies discussed here can seem intimidating---for instance, revocation of privileges or code of conduct violations. It is our hope that we don't have to rely on these guidelines; however, we believe that it is important to have them in place should they be needed. ## Roles The following roles exist in the project: -1. Maintainer: Person with github administrative rights. +1. Maintainer: Person with GitHub administrative rights. -2. Committer: Person with github "Write" privileges; this entails the right and obligation to review PRs by Contributors and to actively participate in discussions. +2. Committer: Person with GitHub "Write" privileges; this entails the right and obligation to review PRs by Contributors and to actively participate in discussions. 3. Contributor: Person that has contributed code. @@ -16,21 +20,21 @@ The following roles exist in the project: ## Relationships between roles -Any User may also be Contributor. Any Contributor may also be Committer. Any Committer may also be Maintainer. A Maintainer must be a Committer. +Any User may also be a Contributor. Any Contributor may also be a Committer. Any Committer may also be a Maintainer. A Maintainer must be a Committer. ## Change of role -Any User may become Contributor by creating a pull request (PR) and getting it successfully reviewed and merged by Committers. +Any User may become a Contributor by creating a pull request (PR) and getting it successfully reviewed and merged by Committers. -Any Contributor can become Committer by contributing sufficient code and displaying deep subject matter knowledge in discussions such that a majority of Committers vote for this change of role. A Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of Committers. +Any Contributor can become a Committer by contributing sufficient code and displaying deep subject matter knowledge in discussions such that a majority of Committers vote for this change of role. A Maintainer can veto such a vote. Such a veto can be overruled by a 2/3 majority of Committers. -As such voting decision may be considered subjective, Contributors striving to become Committers are encouraged to ask for advice by Committers as to what --if anything-- should be done (additionally to already documented knowledge in contributions) to attain this status. Baseline requirements for contributions are documented in [CONTRIBUTING.md](CONTRIBUTING.md). Any Contributor can create a discussion item to request a vote to become Committer. +As such a voting decision may be considered subjective, Contributors striving to become Committers are encouraged to ask for advice by Committers as to what---if anything---should be done to attain this status (additional to already documented knowledge in contributions). Baseline requirements for contributions are documented in [CONTRIBUTING.md](CONTRIBUTING.md). Any Contributor can create a discussion item to request a vote to become Committer. -Any Committer can become Maintainer by majority vote of voting Committers. A current Maintainer can veto such vote. Such veto can be overruled by a 2/3 majority of all Committers. +Any Committer can become a Maintainer by majority vote of voting Committers. A current Maintainer can veto such a vote. Such a veto can be overruled by a 2/3 majority of all Committers. -A Maintainer is not permitted to remove another Maintainer's github privileges. +A Maintainer is not permitted to remove another Maintainer's GitHub privileges. -A Committer automatically may be moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or if voluntarily suspending this status (leave of absence etc.). If a Maintainer loses the Committer status and with this, the Maintainer status (or voluntarily steps down from this role) the Committers have to determine whether a new Maintainer needs to be elected. +A Committer may be automatically moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or by voluntarily suspending this status (e.g., by taking a leave of absence). If a Maintainer loses or relinquishes the Committer status and, hence, the Maintainer status, the Committers have to determine whether a new Maintainer needs to be elected. Any person violating the [code of conduct](CODE_OF_CONDUCT.md], consistently not fulfilling the role responsibilities or other reasons can lose the role held if a simple majority of Committers votes for such removal and no Maintainer vetos that decision. If a Maintainer is to be removed from that role a 2/3 majority of Committers must agree. @@ -40,20 +44,20 @@ Depending on the reason for removal, a Maintainer may be converted to Emeritus s Change of role or changes to this document is subject to voting. -Votes are to be executed by way of open github discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. +Votes are to be executed by way of open GitHub discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. -Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. If such period extends beyond one year, the Committer permanently loses role and rights. The period is documented in this file next to the person's name below. +Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. The period is documented in this file next to the person's name below. If such period extends beyond one year, the Committer loses role and rights. Role and rights may be re-attained via the same process via the voting process described in ["Change of role"](#change-of-role). ## Documentation of roles -Current Maintainer(s) and Committer(s) are to be documented below by way of reference to their github handles. +Current Maintainers and Committers are to be documented below by way of reference to their GitHub handles. -### Maintainer(s) +### Maintainers @baentsch @dstebila -### Committer(s) +### Committers @baentsch @bhess From e0d95abc1f6f373a0f6239300950e0a1a7d47d7a Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Sat, 28 Oct 2023 09:50:08 +0200 Subject: [PATCH 10/12] Make Leave of absence its own section, and clarify some details (#298) --- GOVERNANCE.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1579aa72..7adaf765 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -34,20 +34,24 @@ Any Committer can become a Maintainer by majority vote of voting Committers. A c A Maintainer is not permitted to remove another Maintainer's GitHub privileges. -A Committer may be automatically moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or by voluntarily suspending this status (e.g., by taking a leave of absence). If a Maintainer loses or relinquishes the Committer status and, hence, the Maintainer status, the Committers have to determine whether a new Maintainer needs to be elected. +A Committer may be automatically moved to Contributor status if not actively contributing by discussion or PR review during the last 90 days or by voluntarily suspending this status (e.g., by taking a ["Leave of absence"](#leave-of-absence)). If a Maintainer loses or relinquishes the Committer status and, hence, the Maintainer status, the Committers have to determine whether a new Maintainer needs to be elected. Any person violating the [code of conduct](CODE_OF_CONDUCT.md], consistently not fulfilling the role responsibilities or other reasons can lose the role held if a simple majority of Committers votes for such removal and no Maintainer vetos that decision. If a Maintainer is to be removed from that role a 2/3 majority of Committers must agree. Depending on the reason for removal, a Maintainer may be converted to Emeritus status. Emeritus Maintainers may still be consulted on some project matters, and can be returned to Maintainer status if their availability changes and a simple majority of Committers agrees. +## Leave of absence + +Any Committer may voluntarily step down from the role for a documented period of time, losing voting rights for that time period. The period is documented in this file next to the person's name below. At the end of this time period, the Committer automatically regains their voting rights. + +A leave of absence may not be longer than a year. If the Committer needs to be away for longer than that, they must step down from that role unconditionally, and regaining that role becomes subject of normal procedures to become Committer, as described in ["Change of role"](#change-of-role) above. + ## Voting Change of role or changes to this document is subject to voting. Votes are to be executed by way of open GitHub discussions. No quorum is needed for votes open for 4 weeks. Urgent matters may be decided by majority vote among Maintainers or 2/3 majority by all Committers within an arbitrary voting period. -Any Committer may voluntarily temporarily for a documented period step down from the role losing voting rights for the specified period. The period is documented in this file next to the person's name below. If such period extends beyond one year, the Committer loses role and rights. Role and rights may be re-attained via the same process via the voting process described in ["Change of role"](#change-of-role). - ## Documentation of roles Current Maintainers and Committers are to be documented below by way of reference to their GitHub handles. From 13cf309765c5de56a4a6d443e45809338581d29a Mon Sep 17 00:00:00 2001 From: Douglas Stebila Date: Sun, 29 Oct 2023 14:42:37 -0400 Subject: [PATCH 11/12] Fix typo in Christian's username --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 7adaf765..2c570025 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -67,4 +67,4 @@ Current Maintainers and Committers are to be documented below by way of referenc @bhess @dstebila @thb-sb -@christianpacquin +@christianpaquin From 2feff1481538f472e8c52ba70f66a944a014206c Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Mon, 4 Dec 2023 16:38:21 +0100 Subject: [PATCH 12/12] Update GOVERNANCE.md Co-authored-by: Spencer Wilson --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 2c570025..4207602a 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -44,7 +44,7 @@ Depending on the reason for removal, a Maintainer may be converted to Emeritus s Any Committer may voluntarily step down from the role for a documented period of time, losing voting rights for that time period. The period is documented in this file next to the person's name below. At the end of this time period, the Committer automatically regains their voting rights. -A leave of absence may not be longer than a year. If the Committer needs to be away for longer than that, they must step down from that role unconditionally, and regaining that role becomes subject of normal procedures to become Committer, as described in ["Change of role"](#change-of-role) above. +A leave of absence may not be longer than a year. If the Committer needs to be away for longer than that, they must step down from that role unconditionally, and regaining that role becomes subject of normal procedures to become Committer, as described in ["Change of role"](#change-of-role) above. ## Voting