This Committee is Retired ❤️
The Node.js Community Committee has been retired. You can find the blog post with details here.
The Community Committee is a top-level committee in the Node.js Project focused on community-facing efforts. For details on how we operated, read the Community Committee Charter.
Why does the Community Committee exist?
The Community Committee reflects a formal role and the relevance of the voice of community in the governance of the Node.js project. The formation of this group as a committee alongside the Technical Steering Committee (TSC) demonstrates that community-focused contributions are valued by the contributors of Node.js, and that roles other than those of code contributor help foster a healthy, sustainable open source community.
The Community Committee works to empower people in every part of the project. By focusing on outward-facing community efforts, we aim to make the Node.js project more diverse and improve the environment for inclusivity, attracting a wider range of views, voices, and opinions, which in turn helps us ship better software.
Community Committee initiatives are formed with the intent of improving the cultural development and outreach within the Node.js project, and are therefore suited to engaging people with non-coding skill sets to contribute as well.
code commits !== the only means to contributions.
The Community Committee is tasked with growing and sustaining the Node.js Community. If you're reading this, you're already a part of that community and we'd love to have your help!
Before you get started, here's a broad outline of the Community Committee's governance structure:
- Community Committee: meta-level admin concerns, cross-cutting with other groups like the Node.js TSC, OpenJS Foundation CPC, and Working Groups
- Initiatives: focused on specific tasks, independent from the Community Committee but sharing what they're doing in the Community Committee's bi-weekly meetings.
As seen here, most of the community work that immediately affects the project is done within the numerous initiatives. We recommend checking the list of initiatives below and getting involved with one that you find interesting! If nothing is particularly interesting to you and you have concrete ideas, open an issue here! We can help to point you in the right direction.
To get started with contributing, you should read the Contributing Guidelines document. This document details the roles you can take on. It also includes a guide to contributing and links to
good first issues where we're looking for help.
If you're interested in participating in the Community Committee directly, you're more than welcome to join via the Zoom link posted in our bi-weekly meeting issues.
Initiatives are projects that the Community Committee and the broader community members are collaborating on to enable Node.js across the ecosystem.
At any one time the Node.js Community Committee has a number of strategic initiatives underway. With the less-tangible approach to the work that the Community Committee does, having a way to track this work is important.
For each strategic initiative, the Community Committee's goal is to have a single point of reference - a champion - that understands what's happening with the initiative to the fullest extent possible, and can report on the initiative as needed.
A review of the initiatives will be a standing item on the Community Committee agenda (even if the update is 'nothing new') as a way to ensure they are active and have the support needed.
In Need of Champion
|Code + Learn Friendliness||?||#158|
|How I Got Into Node||?||#138|
|Node.js People Everywhere||?||#184|
|This week in Core||?||#148|
Completed / Retired
|Badges||amiller-gh||nodejs/badges||On pause until design is refined in website-redesign|
|Community Events||Patrick Heneise||nodejs/community-events||Repository Archived|
|Education||hackygolucky||nodejs/education||Absorbed by the Website Redesign Initiative|
|Enterprise User Feedback||AhmadNassri||nodejs/user-feedback||Repository archived|
|Evangelism WG||bnb||nodejs/evangelism||Responsibilities absorbed by CommComm|
|Open-source Friday||?||#180||No clear project|
|Social Media Delegates||bnb||nodejs/social-media-delegates|
|User Feedback||dshaw||nodejs/user-feedback||Moved to OpenJS|
Community Committee meetings are broadcast via Zoom. The join link is published in the meeting's respective issue. Meeting times are coordinated to optimize for contributor timezones.
Current meeting cadence is every other week on Thursdays. Please check the Node.js Project calendar for next scheduled meeting. Also, the issues section of this repo will include a CommComm meeting issue, some time before it begins.
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing on the Node.js YouTube channel when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording and streaming. Please be patient, and it should show up.
Governance and Current Members
The Community Committee is an autonomous committee that collaborates alongside the TSC and whose governance was strongly influenced by the TSC's example. See governance documentation to learn more about the group's evolving structure and CONTRIBUTING.md for guidance about the expectations for all contributors to this project.
Community Committee Members
- AhmadAwais – Ahmad Awais <me@AhmadAwais.com>
- bnb - Tierney Cyren <email@example.com> Community Committee Chair
- joesepi - Joe Sepi <firstname.lastname@example.org> Community Committeee CPC Representative
- mhdawson - Michael Dawson <email@example.com>
- obensource - Ben Michel <firstname.lastname@example.org>
- rachelnicole - Rachel White <email@example.com>
Community Committee Emeriti
- ashleygwilliams - Ashley Williams <firstname.lastname@example.org>
- codeekage - Agiri Abraham Jr. <email@example.com>
- MylesBorins - Myles Borins <firstname.lastname@example.org>
- jpwesselink - JP Wesselink <email@example.com>
- oe - Olivia Hugger <firstname.lastname@example.org>
- gr2m - Gregor Martynus <email@example.com>
- AkashaThone - Akasha Thorne <firstname.lastname@example.org>
- msmichellegar - Michelle Garrett <email@example.com>
- refack - Refael Ackermann <firstname.lastname@example.org>
- jemjam - Jem Bezooyen <email@example.com> Community Committee Secretary
- Tiriel - Benjamin Zaslavsky <firstname.lastname@example.org>
- nebrius - Bryan Hughes <email@example.com> Community Committee Chairperson
- hackygolucky - Tracy Hinds <firstname.lastname@example.org>
- bamieh - Ahmad Bamieh <email@example.com>
- williamkapke - William Kapke <firstname.lastname@example.org>
- amiller-gh - Adam Miller <email@example.com>
- dshaw - Dan Shaw <firstname.lastname@example.org>
- keywordnew - Manil Chowdhury <email@example.com>
- waleedashraf - Waleed Ashraf <firstname.lastname@example.org>