This repository is formal efforts of the Node.js project that are overseen and require input from both the TSC and CommComm.
Initiatives that are overseen here:
Repositories that fall under the responsibility of the TSC and CommComm:
- This repo
- Getting Started
- Collaboration Summit
- The private Moderation repo (Collaborators-only access)
The Admin repo is overseen by the TSC and CommComm as collaborative groups. Any action requiring consensus and voting will abide by the following process.
Members of the TSC and CommComm shall operate under Lazy Consensus as a collaborative unit in the Admin repo hereby referenced as the Admin members. Members shall establish appropriate guidelines for implementing Lazy Consensus (e.g. expected notification and review time periods) within the development process.
The Admin members follow 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 member can call for either a closing vote or a vote to table the issue to the next meeting. The call for a vote must be seconded by a majority of the Admin members or else the discussion will continue.
For all votes, a simple majority of all Admin members for, or against, the issue wins. There must be a simple majority vote in each committee. If an individual happens to be in both committees, then they would end up with two votes. An Admin member may choose to participate in any vote through abstention.
- @ashleygwilliams - Ashley Williams, Individual Membership Director
- @bnb - Tierny Cyren, CommComm Co-Chair
- @hackygolucky - Tracy Hinds, Education + Community at Node.js Foundation
- @mhdawson - Michael Dawson, TSC Chair
- @MylesBorins - Myles Borins, TSC Director
- @rachelnicole - Rachel White, CommComm Co-Chair
- @williamkapke - William Kapke, Individual Membership Director
All active members of the TSC and CommComm.
A calendar of The Foundation's meetings can be found at:
Click +GoogleCalendar at the bottom right to add to your own Google calendar.
The calendar is maintained by:
- @gibfahn - Gibson Fahnestock
- @hackygolucky - Tracy Hinds
- @jasnell - James Snell
- @joshgav - Josh Gavant
- @mcollina - Matteo Collina
- @mhdawson - Michael Dawson
- @nebrius - Bryan Hughes
- @ryanmurakami - Ryan Lewis
- @sam-github - Sam Roberts
- @trott - Rich Trott
- @williamkapke - William Kapke
- @bnb - Tierney Cyren
All calendar maintainers have Make changes AND manage sharing permissions. If you would like to help maintain your team's calendar events, open a PR adding your name to the list above. Once approved, one of the calendar maintainers will add you to the calendar settings.
This list should be reviewed and pruned annually (at minimum). The calendar has a yearly recurring event on Jan 31st for this. An issue should be opened asking the calendar maintainers for their continued volunteering efforts (directly @-mention all members). After 1 week, this list should be PRed removing members that did not respond. The calendar permissions to be updated once merged.
ARCHIVE: This repository was formally Collaboration. Please see the Community Committee repository for information on current efforts around supporting and growing the Node.js Community.