Add Community Committee to the About section #1465

amiller-gh · 2017-11-11T11:45:51Z

Addresses nodejs/community-committee#134

Took a first pass at content, but would love for the CommComm group to help wordsmith it! Have at it.

amiller-gh · 2017-11-11T11:46:17Z

locale/en/about/community.md

+
+# 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!


Do we want to abbreviate to CommComm or CC?

I'd stick with CommComm, that's what it's called most of the time, from what I've seen

I agree with sticking to CommComm.

+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 😄

amiller-gh · 2017-11-11T11:46:42Z

locale/en/about/community.md

+
+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:


Please correct me if anything is wrong or missing!

The CommComm has authority over outward-facing community outreach efforts, including:

I think this may be a bit more concise 😄

amiller-gh · 2017-11-11T11:47:16Z

locale/en/about/community.md

+ - Project Moderation/Mediation
+ - Public Outreach and [Publications](https://medium.com/the-node-js-collection)
+
+There are four levels of engagement with the Community Committee:


Don't know if this is the right verbiage. Engagement? Commitment? Involvement?

I'd go with involvment, engagement seems too definitive for me

I'd add in Internationalization Working Group info

+1 to involvement over engagement 👍

amiller-gh · 2017-11-11T11:48:17Z

locale/en/about/community.md

+
+## Membership
+
+To become a member of the Community Committee, start participating! You must:


Probably a better section intro to be had here.

If you're interested in participating in the Community Committee or the projects it works on, there are a few ways you can get involved:

Suggested change - totally open to feedback/iterations.

amiller-gh · 2017-11-11T11:49:32Z

locale/en/about/community.md

+
+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.


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.

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?

One way to keep on top of meetings (not just CommComm, but all Node.js meetings):

Subscribe to the Node.js Foundation YouTube channel (https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ)

Turn on Channel Notifications:

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 👍

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

amiller-gh · 2017-11-11T11:50:47Z

locale/en/site.json

@@ -39,6 +39,10 @@
            "link": "about/governance",
            "text": "Governance"


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?

I really can't, but totally open to suggestions 😬

Tiriel · 2017-11-11T13:37:02Z

locale/en/about/community.md

+ 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.


This seems a bit misleading to me, but maybe I've got some misconception.
This seems to say that there's some sort of hierarchy between those levels. But, unless I'm wrong, I see two different kind of involvments. Contributor/Collaborator on one side, and Observer/Member on the other side. For instance, you don't have to be Collaborator to become an Observer AFAIK, but this seems to say so.

Maybe at least turn this into a bullet list?

I agree. Lets switch to a bullet list.

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.

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.

Tiriel · 2017-11-11T13:39:19Z

locale/en/about/community.md

+
+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.


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?

Tiriel · 2017-11-11T13:42:52Z

locale/en/about/community.md

+
+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.


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?

I'd err on the side of landing this PR and then updating once nodejs/community-committee#169 is resolved 👍

bnb

Generally LGTM - this could be shipped as-is if needed, but I've included some change requests to optimize it a bit ❤️

bnb · 2017-11-13T18:48:40Z

locale/en/about/community.md

+ 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.


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.

bnb · 2017-11-13T18:51:59Z

locale/en/about/community.md

+To become a member of the Community Committee, start participating! You must:
+
+ 1. Attend the bi-weekly meetings, investigate issues tagged as good first issue, file issues and pull requests, and provide insight via GitHub.
+ 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.


Request to become an Observer by filing an issue (here's an example of a request).

Minor change, adding in an example 😊

bnb · 2017-11-13T18:59:16Z

locale/en/about/community.md

+
+# 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!


+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 😄

bnb · 2017-11-13T19:00:06Z

locale/en/about/community.md

+
+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:


The CommComm has authority over outward-facing community outreach efforts, including:

I think this may be a bit more concise 😄

bnb · 2017-11-13T19:01:08Z

locale/en/about/community.md

+ - Project Moderation/Mediation
+ - Public Outreach and [Publications](https://medium.com/the-node-js-collection)
+
+There are four levels of engagement with the Community Committee:


+1 to involvement over engagement 👍

bnb · 2017-11-13T19:03:28Z

locale/en/about/community.md

+
+## Membership
+
+To become a member of the Community Committee, start participating! You must:


If you're interested in participating in the Community Committee or the projects it works on, there are a few ways you can get involved:

Suggested change - totally open to feedback/iterations.

bnb · 2017-11-13T19:10:10Z

locale/en/about/community.md

+
+To become a member of the Community Committee, start participating! You must:
+
+ 1. Attend the bi-weekly meetings, investigate issues tagged as good first issue, file issues and pull requests, and provide insight via GitHub.


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.

- Attend the bi-weekly CommComm meetings - you can request the bi-weekly meetings by requesting to become an observer (see an example of such a request [here](https://github.com/nodejs/community-committee/issues/142)). Once added as an Observer to meetings, we will track attendance and participation for 3 months as a part of becoming a membership, as defined by the CommComm Governance. - Take on introductory issues labeled as "Good First Issue", file issues with your ideas for what the CommComm can work on, create pull requests with improvements to our existing work, and help us by sharing your thoughts and ideas in the ongoing discussions we're having in GitHub. - Participate in our ongoing efforts around community building - like localization, evangelism, the Node.js Collection, and others - by digging into their respective repositories and getting involved!

bnb · 2017-11-13T19:12:37Z

locale/en/about/community.md

+
+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.


One way to keep on top of meetings (not just CommComm, but all Node.js meetings):

Subscribe to the Node.js Foundation YouTube channel (https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ)

Turn on Channel Notifications:

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 👍

bnb · 2017-11-13T19:14:01Z

locale/en/about/community.md

+
+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.


I'd err on the side of landing this PR and then updating once nodejs/community-committee#169 is resolved 👍

bnb · 2017-11-13T19:14:39Z

locale/en/site.json

@@ -39,6 +39,10 @@
            "link": "about/governance",
            "text": "Governance"


I really can't, but totally open to suggestions 😬

amiller-gh · 2017-11-17T20:44:31Z

Updated with feedback 😁

@bnb, regarding your "one bullet rewrite" 😉 I've re-worked the section headers to improve the document flow a bit and I believe it should cover all the bases you mentioned.

The intro section lays out the four types of involvement Contributor, Collaborator, Observer and Member. The following two sections then deep-dive into Contributors and Collaborators and Observers and Membership. Your rewritten bullets have been integrated into both sections where they seemed to belong, and the Observers and Membership section emphasizes that your work as a Contributor/Collaborator is a factor in becoming a member (Section 3, Item 1).

Attend the bi-weekly CommComm meetings - you can request the bi-weekly meetings by requesting to become an observer (see an example of such a request here). Once added as an Observer to meetings, we will track attendance and participation for 3 months as a part of becoming a membership, as defined by the CommComm Governance.

☝️ This language is items 1, 2 and 3 in Observers and Membership

Take on introductory issues labeled as "Good First Issue", file issues with your ideas for what the CommComm can work on, create pull requests with improvements to our existing work, and help us by sharing your thoughts and ideas in the ongoing discussions we're having in GitHub.

Participate in our ongoing efforts around community building - like localization, evangelism, the Node.js Collection, and others - by digging into their respective repositories and getting involved!

☝️ This language is featured prominently in the Contributors and Collaborators section

Give it a read through and see if it works for you – if you have a more preferred way to structure it, let me know! Happy to keep tweaking.

bnb · 2017-11-28T20:58:03Z

@amiller-gh just went through the changes, and they LGTM! If we need to update later, we can. Thank you VERY much for this contribution! 🙏

ghost

LGTM, let's land this.

Add Community Committee to the About section

43b4c6a

amiller-gh commented Nov 11, 2017

View reviewed changes

amiller-gh mentioned this pull request Nov 11, 2017

Add CommComm Section to Node.js Website nodejs/community-committee#134

Closed

Tiriel reviewed Nov 11, 2017

View reviewed changes

bnb requested changes Nov 13, 2017

View reviewed changes

bnb mentioned this pull request Nov 13, 2017

Lazy consensus with policies vs. people nodejs/community-committee#169

Closed

Updated to reflect feedback

536af03

amiller-gh force-pushed the master branch from 843214e to 536af03 Compare November 17, 2017 20:47

Tiriel approved these changes Nov 17, 2017

View reviewed changes

bnb approved these changes Nov 28, 2017

View reviewed changes

ghost approved these changes Nov 29, 2017

View reviewed changes

ghost merged commit c615db0 into nodejs:master Nov 29, 2017

Riveoxx mentioned this pull request Aug 1, 2022

[Snyk] Security upgrade node-fetch from 2.6.1 to 3.2.10 Riveoxx/nodejs.org#16

Open

ryan-ally mentioned this pull request Aug 1, 2022

[Snyk] Security upgrade node-fetch from 2.6.0 to 3.2.10 ryan-ally/nodejs.org#53

Merged

MarcelRaschke mentioned this pull request Aug 19, 2022

[Snyk] Upgrade node-fetch from 2.6.7 to 3.2.9 MarcelRaschke/nodejs.org#67

Open

This pull request was closed.


		# 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 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:


		## Membership

		To become a member of the Community Committee, start participating! You must:


		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.

		@@ -39,6 +39,10 @@
		"link": "about/governance",
		"text": "Governance"


		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.


		To become a member of the Community Committee, start participating! You must:

		1. Attend the bi-weekly meetings, investigate issues tagged as good first issue, file issues and pull requests, and provide insight via GitHub.

Add Community Committee to the About section #1465

Add Community Committee to the About section #1465

Conversation

amiller-gh commented Nov 11, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bnb Nov 13, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bnb left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bnb Nov 13, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

amiller-gh commented Nov 17, 2017

bnb commented Nov 28, 2017

ghost left a comment • edited by ghost Loading

Choose a reason for hiding this comment

bnb Nov 13, 2017 •

edited

Loading

bnb Nov 13, 2017 •

edited

Loading

ghost left a comment •

edited by ghost

Loading