The goal of this document is to provide a set of shared context for new and existing Community Committee members to work from.
Community Committee members are held to following the Membership Policy.
- The Community Committee repository is the administrative repository for CommComm discussions.
- The Admin repository is a place for meta-discussions about the project, GitHub org, travel fund, and so on between the Node.js Community Committee and the Node.js Technical Steering Committee.
- The Moderation repository (a private repository) is for tracking issues related to Moderation.
- Many CommComm Strategic Initiatives operate in their own repositories. A list of active initiatives can be found in the main README.
There is a travel fund available to all contributors to the Node.js project, in addition to all collaborators on OpenJS Foundation projects.
The Node.js project has adopted open source practices to organize our efforts, interactions, and complete administrative duties related to our work. What follows is a quick guide to how we do things, to get you started!
Consensus is the first choice for making decisions. The CommComm uses a "consensus-seeking" model for issues that are escalated to the committee.
The group looks for a resolution, one with no open objections, among the CommComm members. If a consensus with no objections can't be reached, then a vote is called. A simple majority in the vote indicates the decision to be followed.
We aim for the majority of decisions made by the CommComm to be achieved through the consensus-seeking process. Voting is only used as a last resort.
Issues in Github are what we use to begin discussions. They have the advantage of being async and let people contribute over time.
Pull requests in Github are what we use to put documents, code, and other material into the project. PRs have the advantage of giving everyone involved time and space to add material, suggest changes, and discuss the contribution.
Before landing pull requests, sufficient time should be left for input from other Collaborators. Leave 72 hours to account for international time differences and work schedules. Trivial changes (e.g., typos or content changes) may be landed after a shorter delay.
Where there is no disagreement amongst Collaborators, a pull request may be landed given an appropriate review. Where there is a discussion amongst Collaborators, consensus should be sought if possible. The lack of consensus may indicate the need to elevate the discussion to the Community Committee Members for resolution