Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nodejs/admin
Administrative space for policies of the TSC
https://github.com/nodejs/admin
node nodejs
Last synced: 28 days ago
JSON representation
Administrative space for policies of the TSC
- Host: GitHub
- URL: https://github.com/nodejs/admin
- Owner: nodejs
- Created: 2015-08-09T23:47:00.000Z (about 9 years ago)
- Default Branch: main
- Last Pushed: 2024-03-21T14:03:44.000Z (8 months ago)
- Last Synced: 2024-04-14T00:38:23.667Z (7 months ago)
- Topics: node, nodejs
- Homepage:
- Size: 4.75 MB
- Stars: 147
- Watchers: 53
- Forks: 127
- Open Issues: 62
-
Metadata Files:
- Readme: README.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome - nodejs/admin - Administrative space for policies of the TSC (JavaScript)
README
# Administration Documents for Node.js
This repository is formal efforts of the Node.js project that are overseen by the
[TSC](https://github.com/nodejs/TSC) regarding the less technical aspects of the project.It is also used to discuss:
- [Getting Started](https://github.com/nodejs/getting-started)
- The private [Moderation](https://github.com/nodejs/moderation) repo (Collaborators-only access)## Travel Fund
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](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/project-resources/MEMBER_TRAVEL_FUND.md).## Collaborator Summit
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](https://github.com/openjs-foundation/summit).## Governance and Current Members
The Admin repo is overseen by the [TSC](https://github.com/nodejs/TSC). Any
action requiring consensus and voting will abide by the TSC process for that.### Contacts for assistance
- [@mcollina](https://github.com/mcollina) - **Matteo Collina**, TSC Vice Chair
- [@mhdawson](https://github.com/mhdawson) - **Michael Dawson**, TSC Chair### Admin members
All voting members of the TSC.
## Social Team
The currently active members of the [Social Team](./social-team.md):
- [@joesepi](https://github.com/joesepi) - **Joe Sepi**
## Node.js 1Password
Thanks to 1Password's [open-source program](https://github.com/1Password/1password-teams-open-source),
Node.js has been comped a paid version of 1Password, managed by the TSC chair person.### 1Password Groups
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.
#### Current Groups
- **Social Team:** For the [Social Team](#social-team) to contain official account credientials.
## @nodejs-github-bot
Follow the steps in [request-an-access-token](./request-an-access-token.md) to request an access token under the name of [`@nodejs-github-bot`][].
## Node.js Project Calendar
A calendar of the project's meetings can be found at:
https://nodejs.org/calendar
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](https://support.google.com/a/answer/117596?hl=en).
### Calendar Maintainers
- [@bethgriggs](https://github.com/bethgriggs) - **Beth Griggs**
- [@bnb](https://github.com/bnb) - **Tierney Cyren**
- [@gireeshpunathil](https://github.com/gireeshpunathil) - **Gireesh Punathil**
- [@joesepi](https://github.com/joesepi) - **Joe Sepi**
- [@marco-ippolito](https://github.com/marco-ippolito) - **Marco Ippolito**
- [@mcollina](https://github.com/mcollina) - **Matteo Collina**
- [@mhdawson](https://github.com/mhdawson) - **Michael Dawson**
- [@MylesBorins](https://github.com/MylesBorins) - **Myles Borins**
- [@ruyadorno](https://github.com/ruyadorno) - **Ruy Adorno**
- [@trott](https://github.com/trott) - **Rich Trott**[`@nodejs-github-bot`]: https://github.com/nodejs-github-bot