This repository is formal efforts of the Node.js project that are overseen and require input from both the TSC and CommComm.
Repositories that fall under the responsibility of the TSC and CommComm:
- This repo
- Getting Started
- The private Moderation repo (Collaborators-only access)
Each member of the Node.js organization can ask for funding to travel and spread knowledge about and support the Javascript ecosystem and the Foundation.
The management of Travel Fund for collaborators is managed by the OpenJS Foundation Cross-Project-Council.
Every year, Node.js collaborators meet up in one or more Collaborator Summit. If you are interested in joining or helping with the organization, the management of Collaborators Summit is managed by the OpenJS Foundation Summit team.
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.
For all votes, the vote must pass in both TSC and CommComm or else the motion fails. If an individual happens to be in both committees, then they would end up with two votes.
- @bnb - Tierney Cyren, CommComm Chair
- @joesepi - Joe Sepi, CommComm OpenJS Representative
- @mhdawson - Michael Dawson, TSC Chair
- @mmarchini - Mary Marchini, TSC OpenJS Representative
All active members of the TSC and CommComm.
The currently active members of the Social Team:
Thanks to 1Password's open-source program, Node.js has been comped a paid version of 1Password.
There will always be two owners of this account - the TSC and CommComm chairpeople. These owners are expected to use their access only to maintain the account and not for access to credientials that they do not otherwise explicitly have access to through Groups within.
Groups are created in 1Password with a 1:1 mapping of Node.js organization teams, as requested. Groups are asssigned to Vaults, which contain distinct sets of credentials that should only be used by the Groups that are provided access to them. If there is a team in the Node.js organization that would like to have a Group for your Node.js organization team, please PR an addition to the list below and request the current account owners as reviewers on the PR.
- Social Team: For the Social Team to contain official account credientials.
A calendar of the project's meetings can be found at:
Click +GoogleCalendar at the bottom right to add to your own Google calendar.
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.
- @bethgriggs - Beth Griggs
- @bnb - Tierney Cyren
- @gireeshpunathil - Gireesh Punathil
- @joesepi - Joe Sepi
- @mcollina - Matteo Collina
- @mhdawson - Michael Dawson
- @MylesBorins - Myles Borins
- @ryanmurakami - Ryan Lewis
- @trott - Rich Trott