-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Community Committee to the About section #1465
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
--- | ||
title: Community Committee | ||
layout: about.hbs | ||
--- | ||
|
||
# Community Committee | ||
|
||
The Community Committee (CommComm) is a top-level committee in the Node.js Foundation focused on community-facing efforts. Code commits !== the only way to contribute! | ||
|
||
The CommComm has authority over community outreach including: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please correct me if anything is wrong or missing! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I think this may be a bit more concise 😄 |
||
- Community Evangelism | ||
- Education Initiatives | ||
- Cultural Direction of Node.js Foundation | ||
- Community Organization Outreach | ||
- Project Moderation/Mediation | ||
- Public Outreach and [Publications](https://medium.com/the-node-js-collection) | ||
|
||
There are four levels of engagement with the Community Committee: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't know if this is the right verbiage. Engagement? Commitment? Involvement? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd go with involvment, engagement seems too definitive for me There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd add in Internationalization Working Group info There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 to involvement over engagement 👍 |
||
|
||
1. A **Contributor** is any individual creating or commenting on an issue or pull request. | ||
2. A **Collaborator** is a contributor who has been given write access to the repository | ||
3. An **Observer** is any individual who has requested or been requested to attend a CommComm meeting. It is also the first step to becoming a Member. | ||
4. A **Member** is a collaborator with voting rights who has met the requirements of participation and voted in by the CommComm voting process. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems a bit misleading to me, but maybe I've got some misconception. Maybe at least turn this into a bullet list? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree. Lets switch to a bullet list. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. TIL that "Collaborator" is an official class of participation in the CommComm, as defined in our Charter. We've strayed from that, mostly using Contributor, Observer, and Member - so we may need to go update the Charter in a bit here 😅 I do think the structure here is good, since it is the typical flow of how you'd go from being a contributor to a member, but definitely +1 to changing this to a bullet list. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. TIL that "Collaborator" is an official class of participation in the CommComm, as defined in our Charter. We've strayed from that, mostly using Contributor, Observer, and Member - so we may need to go update the Charter in a bit here 😅 I do think the organization right now is good, since it's the general flow of how you'd go from being a collaborator to a member, but definitely +1 to making it bullets instead of a list. |
||
|
||
For the current list of Community Committee members, see the project's [README.md](https://github.com/nodejs/community-committee). | ||
|
||
## Collaborators | ||
|
||
It is the mission of CommComm to further build out the Node.js Community. If you're reading this, you're already a part of that community – and as a part of the Node.js Community, we'd love to have your help! | ||
|
||
The [nodejs/community-committee](https://github.com/nodejs/community-committee) GitHub repository is a great place to start. Check out the [issues labeled "Good first issue"](https://github.com/nodejs/community-committee/labels/good%20first%20issue) to see where we're looking for help. If you have your own ideas on how we could engage and build the community, feel free to create your own issue. | ||
|
||
If you're interested in participating in the Community Committee as a member, you should create an issue asking to be an Observer in our next Community Committee meeting. You can find a great example of such an issue [here](https://github.com/nodejs/community-committee/issues/142). | ||
|
||
Before diving in though, please be sure to read the [Collaborator Guide](https://github.com/nodejs/community-committee/blob/master/COLLABORATOR_GUIDE.md). | ||
|
||
## Membership | ||
|
||
To become a member of the Community Committee, start participating! You must: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Probably a better section intro to be had here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change - totally open to feedback/iterations. |
||
|
||
1. Attend the bi-weekly meetings, investigate issues tagged as good first issue, file issues and pull requests, and provide insight via GitHub. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I started rewriting this one bullet, but it quickly grew beyond what a single bullet should be 😬 I'd like to suggest a full rework of this section - feel free to modify or suggest any changes.
|
||
2. Request to become an Observer by filing an issue. Once added as an Observer to meetings, we will track attendance and participation for 3 months, as according to our governance guidelines. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Minor change, adding in an example 😊 |
||
3. When you meet the minimum attendance and participation expectations, the CommComm will vote to add you as a member. | ||
|
||
Membership is for 6 months. The group will ask on a regular basis if the expiring members would like to stay on. A member just needs to reply to renew. There is no fixed size of the CommComm. However, the expected target is between 9 and 12. You can read more about membership, and other administrative details, in our [Governance Guide](https://github.com/nodejs/community-committee/blob/master/GOVERNANCE.md). | ||
|
||
Regular CommComm meetings are held bi-monthly in a Zoom video conference, and broadcast live to the public on YouTube. Meeting announcements and agendas are posted before the meeting begins in the organization's [GitHub issues](https://github.com/nodejs/community-committee/issues). Any community member or contributor can ask that something be added to the next meeting's agenda by logging a GitHub Issue. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a better way for newbies to discover when/how meetings are held? Right now its "keep an eye out on the issues list for the announcement". Not the easiest way for those not plugged in yet to engage. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe advertise the timing of the meetings? Although I realize it's subject to change. But we know it's definitely on thursday at a precise UTC hour? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One way to keep on top of meetings (not just CommComm, but all Node.js meetings):
That will alert anyone interested in when a livestream is going online, and (if the stream is scheduled beforehand, something @rachelnicole and I need to work on doing) get notice well before the stream is actually live 👍 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It should also be on the standard calendar, and its at a regular time so unless it changes it should be easy to know when the next one is: https://nodejs.org/calendar |
||
|
||
## Consensus Seeking Process | ||
|
||
The CommComm follows a [Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 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 a consensus cannot be reached that has no objections then a majority wins vote is called. It is expected that the majority of decisions made by the CommComm are via a consensus seeking process and that voting is only used as a last-resort. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It may be a bit too early, but #169 of CommCoom seems to indicate we all agree on the principle. So maybe we can add a bit on the Condorcet voting? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd err on the side of landing this PR and then updating once nodejs/community-committee#169 is resolved 👍 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,6 +39,10 @@ | |
"link": "about/governance", | ||
"text": "Governance" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note: The TSC is still under a tab called "Governance". We are under a new side bar called "Community". There is definitely a better IA for the site. Figured we'd save that for a larger re-design though. Can anyone think of a better stop-gap solution? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I really can't, but totally open to suggestions 😬 |
||
}, | ||
"community": { | ||
"link": "about/community", | ||
"text": "Community" | ||
}, | ||
"workinggroups": { | ||
"link": "about/working-groups", | ||
"text": "Working Groups" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to abbreviate to
CommComm
orCC
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd stick with CommComm, that's what it's called most of the time, from what I've seen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with sticking to CommComm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to CommComm - I believe CC was confusing with the former CTC, but since that was absorbed into the TSC we've stuck with CommComm 😄