Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: define Committer role, remove expectations from Decision Making #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: define Committer role, remove expectations from Decision Making #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions CGCharter-1727386911.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,13 +234,10 @@ <h2 id="decision">
Decision Process
</h2>
<p>
This group will seek to make decisions where there is consensus. The Group makes decisions in the following ways: either Participants who have
earned Committer status for a history of useful contributions assess
This group will seek to make decisions where there is consensus. The Group makes decisions in the following ways: either Committers assess
consensus, or the Chair assesses consensus, or where consensus isn't
clear there is a Call for Consensus [CfC] (see below) to allow multi-day
online feedback for a proposed course of action. It is expected that
participants can earn Committer status through a history of valuable
discursive contributions as is common in open source projects.
online feedback for a proposed course of action.
After discussion and due consideration of different opinions, a decision
should be publicly recorded (where GitHub is used as the resolution
of an Issue).
Expand Down Expand Up @@ -464,6 +461,14 @@ <h2 id="offboarding-chairs">
</li>
</ul>

<h2 id="committers">
Committers
</h2>

<p>
A <dfn>Committer</dfn> is authorized to make changes to one or more GitHub repositories that are managed by the group. Participants can earn Committer status through a history of useful contributions. Granting Committer status is made through consensus, as discussed in <a href="#decision">Decision Process</a>. There is no limit to the number of Committers in the group or on a repository. There is no time limit on Committer status. Each repository should have at least one active Committer. Chair(s) can revoke Committer status for any reason. A Committer can give up the role voluntarily.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A <dfn>Committer</dfn> is authorized to make changes to one or more GitHub repositories that are managed by the group. Participants can earn Committer status through a history of useful contributions. Granting Committer status is made through consensus, as discussed in <a href="#decision">Decision Process</a>. There is no limit to the number of Committers in the group or on a repository. There is no time limit on Committer status. Each repository should have at least one active Committer. Chair(s) can revoke Committer status for any reason. A Committer can give up the role voluntarily.
A <dfn>Committer</dfn> is authorized to make changes to one or more GitHub repositories that are managed by the group. Participants can earn Committer status through a history of useful contributions. Granting Committer status is made through consensus, as discussed in <a href="#decision">Decision Process</a>. There is no limit to the number of Committers in the group or on a repository. There is no time limit on Committer status. Each repository for ongoing work items should have at least one active Committer other than the Chairs. Chair(s) can revoke Committer status for any reason. A Committer can give up the role voluntarily.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm not wed to this little suggestion, and it kinda goes without saying since all work items have "champions" in the staging process anyways, but thought it might be a helpful reminder to give write privileges to one or more key participants any time a new repo is made 😄

</p>

<h2 id="charter-change">
Amendments to this Charter
</h2>
Expand Down