Skip to content

Latest commit

 

History

History
208 lines (143 loc) · 9.09 KB

GOVERNANCE.md

File metadata and controls

208 lines (143 loc) · 9.09 KB
Raw

OpenJS Cross Project Council

For the current list of Team members, see the project README.md.

Members

The openjs-foundation/cross-project-council GitHub repository is maintained by the Team and additional Members who are added on an ongoing basis.

Team Membership

Team Membership is not time-limited. There is no fixed size of the Team.

There is no specific set of requirements or qualifications for Team Membership beyond these rules.

The following groups automatically have membership and can request to be added to the github team:

  • OpenJS Foundation Voting Members
  • OpenJS Foundation Regular Members
  • OpenJS Foundation Board of Directors
  • OpenJS Foundation Project Maintainers

Team Meetings

The Team meets weekly on Zoom.us. A designated moderator approved by the Team runs the meeting. Each meeting should be published to YouTube.

Items are added to the Team agenda that are considered contentious or are modifications of governance, contribution policy, Team membership, or release process.

The intention of the agenda is not to approve or review all patches; that should happen continuously on GitHub and be handled by the larger group of Collaborators.

Any community member or contributor can ask that something be added to the next meeting's agenda by logging a GitHub Issue. Any Collaborator, Team member or the moderator can add the item to the agenda by adding the cross-project-council-agenda label to the issue.

Prior to each Team meeting the moderator will share the agenda with members of the Team. Team members can add any items they like to the agenda at the beginning of each meeting. The moderator and the Team cannot veto or remove items.

The moderator is responsible for summarizing the discussion of each agenda item and sends it as a pull request after the meeting.

Consensus Seeking Process

The Team follows a Consensus Seeking decision-making model.

When an agenda item has appeared to reach a consensus, the moderator will ask "Does anyone object?" as a final call for dissent from the consensus.

If an agenda item cannot reach a consensus, a Team member can call for the item to be decided by a vote or to table the issue to the next meeting. In both cases the decision must be seconded by a majority of the Team or else the discussion will continue. Simple majority wins. Only Active Members participate in a vote.

Term for Voting Members

As per the CPC charter, the term for all voting members is normally 1 year:

Voting members serve for a term of 1 year and must be re-nominated and ratified by the Voting CPC members each year.

Due to the bootstrap process, the term for the first year will be shortened such that the initial term for all voting members ends March 31st, 2020. Subsequent terms will be for a period of 1 year ending the following March 31st.

Term for CPC Board representatives

As per the CPC charter, the term for CPC Board representatives is 1 year. Due to the bootstrap process, the term for the first year will be adjusted such that the initial term for all CPC Board representatives will end June 30th, 2020. Subsequent terms will be for a period of 1 year ending the following June 30th.

Election process for Non-Impact Voting CPC members

As per the CPC charter, the non-impact projects elect 2 voting CPC members:

up to two (2) Voting members may be nominated by the non-impact projects based on a process set by the CPC.

These members will be elected for a term of 1 year as follows:

  • Once a year an issue will be opened in the CPC repo announcing that the period for nominations is open.

  • Any member from one of the non-impact projects can self-nominate emailing the chair of the CPC with their interest in running for the CPC.

  • The nomination period will be open for 2 weeks at which point the CPC chair will list the nominees in the issue.

  • Each of the candidates listed will be asked to open an issue in the CPC repo which includes the following:

    • Projects they are part of
    • Description of their background
    • The reasons they would like to act as a non-impact CPC voting member
    • Confirmation that they can devote the required time/effort.
    • Their employer (if applicable). This is needed due to the limitations on maximum employer representation in the CPC voting members.

  • The projects will be asked to confirm membership as identified by the nominees.

  • Each non-impact project will nominate two voters through a process of their choosing.

  • Each voter will be able to vote for as many or as few candidates as they wish.

  • Those candidates who receive the greatest number of votes will be confirmed as the winners. In the case of a tie between 2 or more candidates, the winner will be chosen randomly unless:

    • There are only 2 candidates tied for the largest number of votes, in which case those 2 candidates will be the winners, or
    • all but one of the candidates that are tied for the number of votes choose to conceed.

Approving and Onboarding Regular Members

Regular members can self-nominate by opening a PR to add themselves to the Regular member list in the README.md. The PR should include an indication of which project they have been active in for 3 months as per the CPC charter.

The PR to add a regular member is approved when:

  • There are no outstanding objections
  • There are two or more approvals by voting CPC members
  • The PR has been opened for at least 1 week

Once a PR is ready to be landed, the CPC member who lands the pull request should:

  • Send a notification to the project contacts for the project identified in the PR indicating that a new regular CPC member has joined the CPC on behalf of the project.
  • Add the member to the github cpc-regular-members team
  • Add the member to the cpc-private email list
  • Introduce the new member at the next CPC meeting.

Approving Project Charters

Per the CPC charter section 5, the voting CPC members are responsible for approving project charters and changes to them.

Approval of the initial charter or changes to an existing charter will be requested by opening an issue requesting approval in the cross-project-council repository.

The request is approved when:

  • There are no outstanding objections
  • There are two or more approvals by voting CPC members
  • The board has been consulted in the case of substantial changes
  • The issue has been open for at least 14 days

Merging PRs into this Repository

Pull requests that do not change the charter or governance of the CPC can be merged into this repository provided the following conditions have been met:

  • There are no outstanding objections
  • There are two approvals by CPC members
  • The PR has been open for at least 72 hours

Pull requests that change governance of the CPC (including approving changes to Working Groups) must meet the following conditions in addition to the ones listed for regular PRs.

  • The PR has been open for at least 14 days OR consensus is reached in a meeting with quorum of voting members.

Pull requests that change the charter of the CPC must meet the following conditions in addition to the ones listed for changing CPC governance:

  • The text of the PR must be approved by a simple majority of the voting members.
  • The text of the PR must be approved by the board.

If consensus cannot be reached, a pull request may still be landed after a vote by the Voting CPC members to override outstanding objections.

Fast-Tracking PRs

Special exception is made for pull requests seeking to make any of the following changes to this repository:

  • Errata fixes.
  • Editorial changes.
  • Meeting minutes.
  • Updates to the team lists.
  • Doc Fixes.

Charter changes cannot be fast-tracked.

To propose fast-tracking a pull request, apply the fast-track label. Then add a comment that CPC members may upvote.

If someone disagrees with the fast-tracking request, remove the label. Do not fast-track the pull request in that case.

The pull request may be fast-tracked if two CPC members approve the fast-tracking request. To land, the pull request itself still needs two CPC member approvals.

CPC members may request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt.