nodejs / community-committee Goto Github PK

as per convo in the public board meeting, create a form letter to send to global groups for outreach (get translations, etc) cc/ @williamkapke @hackygolucky

Hey everyone,

As I'm trying to re-organize Node Together so it can start happening again we've been trying to figure out a way for it to be a viable organization. Either that means becoming an entity and soliciting money from sponsorship, or trying to become a part of the Node Foundation org.

I think the latter would be the easiest and smoothest, and potentially best way to get valuable input from people in the community on beginner education & outreach to underrepresented minorities.

I would love for it to live under the jurisdiction of CommComm, as I feel that we're best geared towards the basic principals that Node Together stands for, thanks to the great mission @ashleygwilliams put together in founding it.

I'd like to propose we have a discussion / vote during the meeting on whether or not to move forward with the process.

@hackygolucky can provide a bit more insight to the viability of these options, as it's something she previously looked into last fall before I was brought on as the new organizer.

The next collaborator's summit is coming soon! It will be held on May 4th and 5th in Berlin, right before JSConf EU. Details are at openjs-foundation/summit#41.

What would we like to discuss at the collaborator's summit for the CommComm?

Hi. I'm currently on the Node.js Foundation Marketing Committee. I've been wanting to be involved in the foundation more from a community and/or technical standpoint. I am currently moving to different team within IBM and figured now would be a good time to make a change. My goal is to participate in this committee and to start to contribute more technically as well. As a dev advocate for IBM, it may make sense for me to get involved with the evangelism group as well, but as I understand it, that group will be a part of this committee soon as well, correct? Irregardless*...

Thanks.

(* not a word)

As mentioned in last week's CommComm meeting, I've had several people come and ask me how to get involved. I've realized that there's no actual instruction on how, where, or what people can get involved with.

I'd like to ask that we create a contributing guide as a place to get started and point people to when they ask how they can get involved.

Per a discussion with @ZibbyKeaton (also including @hackygolucky and @williamkapke) in the Node.js Foundation Marketing Committee meeting earlier today, I'd like to ask about getting more involvement around the Community Committee having involvement as technical editors for the Node.js Collection.

Previously, this task has entirely fallen on the shoulders of @nodejs/evangelism - I'd love to see if the two groups could collaborate and share this responsibility to improve the flow and get a deeper level of technical and community-centric editing into the process.

Another topic of discussion around this is one that @williamkapke raised that flows into this discussion well: having a more open medium (no pun intended) for reviewers to collaborate on this process. I'd love to discuss this more and see how we can see this evolve into a streamlined way to get articles reviewed, approved, and published with a second iteration of the review process.

For what it's worth, here's some links to issues for background context on the Node.js Collection:

• The initial issue, created by @ZibbyKeaton, proposing the Node.js Collection to the Evangelism WG and detailing guidelines and structure.
  • This could/should be moved into a doc for easier access/linking/reference - good low-barrier contribution to this 😊
• An example of one of the weekly threads that Zibby creates in the Evangelism WG for submissions to review
• The Node.js Collection Announcement Post

Was reviewing CONTRIBUTING.md as a part of creating a new Contributing guide, and I noticed that the word "Collaborator" was still being used - instead of "Member" (ref: #49).

Here are the two documents where this word is still in place:

• CONTRIBUTING.md
• COLLABORATOR_GUIDE.md

If the Community Committee has moved away from the idea of a "Collaborator", these should probably be updated 🤔

CommComm Travel Allocation Request for 2017 for Board deck

We would like to encourage as many collaborators to attend/represent at Collab Summit and other relevant events for the remainder of this year, and part of that is making sure it is known that everyone meeting in one place is awesome(and valued) on our non-technical contribution side as well! This estimate is with the hope that all of this will not be needed, but we'll want to heavily evangelize this to all collaborators because we've been hearing a lot of feedback of the financial challenge it can be to attend these events. Calculating for members of CommComm and the Evangelism WG and reducing the count for employees of corporate members, with a North America to non-NA ratio at 60/40, and estimated at a $500 domestic/$1000 international flight rate, I expect at 2 nights' hotel:

***a general rule for our travel funds is that if you are an employee of a corporate member in Node.js, we ask that you refrain from requesting from the public fund and instead ask your employer. We are happy to help provide information on the value of these events.

Total Allocation Request: $22, 200

This allocation will be contingent upon the Board's approval of the fund being established in #81

The links to GOVERNANCE and CONTRIBUTING are both broken (send you to a 404) in the README.md.

Took a look, and this is because of the file extension on both files - the actual extensions are .MD and the linked extensions are .md. What you typically see is .md, but not sure if changing the file extension at this point would be destructive to the commit history.

Node.js Foundation Community Committee (CommComm) Meeting 2017-06-08

Time

UTC Thu 08-Jun-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee%20(CommComm)+Meeting+2017-06-08&iso=20170608T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+08%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/14Pd6e40n1wPEuRBknDJUFwlf9XDhWI94jCgMEvTfVS4/
• Previous Minutes Google Doc: https://docs.google.com/document/d/1urhinDNJK-EEMziNob8-mlsOEZM_zecluDIgBA6kVOw/

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/community-committee

• Create official secretary position #64
• Move Node Together Repo as an org under CommComm #63
• Request to move nodejs/education under CommComm #46
• Adding folks as members #38
• Moderation shortage #33

nodejs/nodejs-collection

• Refreshing Node.js Collection Review Process and Gathering Technical Editors #1

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Penny Hugger @pup (observer)
• Rachel White @rachelnicole (CommComm)
• Richard Littauer @RichardLitt (observer)
• Rod Vagg @rvagg (CommComm)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)
• Michelle Garrett (msmichellegar) (CommComm)
• Micheal Dawson @mhdawson (observer)
• Tierny Cyren @bnb (observer)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Link to view the event: https://www.youtube.com/watch?v=r5gL9sL3vyM
Link to participate: https://hangouts.google.com/hangouts/_/ytl/uXRMUBslCf5uMiqB95YK3gdaTARSxy4wtDxOFy9ET_c=?eid=100598160817214911030

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

Meeting 2017-04-27Community Committee (CommComm)

Time

UTC Thu 27-Apr-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation++Meeting+2017-04-27&iso=20170427T2030
• or http://www.wolframalpha.com/input/?i=8:30pm+UTC%2C+Apr+27%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1YevHuA_csoTltDJ6mHr21fetZshNqWpsRbBRkSHhmYE/
• Previous Minutes Google Doc: https://docs.google.com/document/d/18d2XeUP_dB4dyLzjO6wqs6NiaSaUxLFDyXYL_HFTEDc

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/board

• Clarify By-Laws WRT Community Committee #57

nodejs/community-committee

• Moderation shortage #33
• Elect a Chairperson #30
• Collaborator's Summit agenda #28
• governance: who has voting rights? #21
• Add some scope (aka: stake your claim!) #13
• Central communication medium for chatting in Node.js #11
• Adding folks as members #38

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• James Snell @jasnell (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Rachel White @rachelnicole (CommComm)
• Rod Vagg @rvagg (CommComm)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts link

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

I noticed that some projects/repos/WGs have copied the full text of a version of the CoC. IF we want to make changes/additions/revisions - it makes it... hard 👎

Can/Should we have just the 1 copy of the CoC?

The primary copy

https://github.com/nodejs/node/blob/master/CODE_OF_CONDUCT.md

Copies I found

(I didn't diff them to see if they are identical or not)
https://github.com/nodejs/community-committee/blob/master/CODE_OF_CONDUCT.MD
https://github.com/nodejs/community-committee/blob/master/COLLABORATOR_GUIDE.MD

https://github.com/nodejs/post-mortem/blob/master/CONTRIBUTING.md
https://github.com/nodejs/benchmarking/blob/master/CONTRIBUTING.md
https://github.com/nodejs/http2/blob/master/CODE_OF_CONDUCT.md
https://github.com/nodejs/evangelism/blob/master/CONTRIBUTING.md
https://github.com/nodejs/Intl/blob/master/CONTRIBUTING-draft.md
https://github.com/nodejs/nodejs-uk/blob/master/CONTRIBUTING.md
https://github.com/nodejs/nodejs.org/blob/master/COLLABORATOR_GUIDE.md
https://github.com/nodejs/docs/blob/master/CONTRIBUTING.md
https://github.com/nodejs/nodejs-hu/blob/master/content/en/working-groups.md

These are special cases:

https://github.com/nodejs/node-chakracore/blob/master/CODE_OF_CONDUCT.md
https://github.com/nodejs/iojs.org/blob/master/CONTRIBUTING.md
https://github.com/nodejs/inclusivity/blob/master/CODE_OF_CONDUCT.md
https://github.com/nodejs/node-convergence-archive/blob/master/CONTRIBUTING.md
https://github.com/nodejs/docker-node/blob/master/GOVERNANCE.md
https://github.com/nodejs/docker-iojs/blob/master/GOVERNANCE.md

Node.js Foundation Community Committee (CommComm) Meeting 2017-07-06

Time

UTC Thu 06-Jul-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee%20(CommComm)+Meeting+2017-07-06&iso=20170706T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jul+06%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1utEp06Pyk0uwJn77TWdxIpwuoiFRjHvKinSdbY1BwNk/
• Previous Minutes Google Doc: https://docs.google.com/document/d/1GXbfPhfbLTr7g9Hp7YP-M60ux_Ua2z8XRXg__me4u4k/

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/TSC

• Candidate "areas" for TSC and Community Committee #278
• meta: moderation policy updates #276

nodejs/community-committee

• Adding Jenn, Tierney, Michael, Olivia, and Richard as members #77

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• Jenn Turner @renrutnnej (observer)
• Joe Sepi @joesepi (observer)
• JP Wesselink @jpwesselink (CommComm)
• Myles Borins @MylesBorins (CommComm)
• Olivia Hugger @pup (observer)
• Rachel White @rachelnicole (CommComm)
• Richard Littauer @RichardLitt (observer)
• Rod Vagg @rvagg (CommComm)
• Tierney Cyren @bnb (observer, note taker)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

I've been thinking about this for a while now, and I think we should create an official secretary role in CommComm. This person (people?) would serve as the official note taker during meetings. This person would be voted on in the same way as chairperson, and would also be called out in the README as holding this role so we can properly give attribution and thanks for this role. It's a really important and thankless role, and I think we should recognize those that decide to take this on.

Sometimes it's necessary to lock a thread, as we did recently in nodejs/node. Other times, it's more appropriate to leave the thread unlocked but moderate certain users. We currently do not have any guidelines on when we should lock vs moderating individuals, nor do we have guidelines for collaborators on how to engage in a locked thread.

Let's get some discussion going here on this and come up with a proposal!

With regard to #46, I'm wondering if there is any existing documentation for criteria or process around transitioning a WG/Team/Other from the TSC into the CC (and the reverse).

If there's not already existing documentation, I'd like to propose creating it and getting feedback on the exact steps that need to go into it. Happy to write this documentation myself, but there's a lot of context that I know I don't have (particularly on the TSC and Governance side of things) that several CC members do have that I think is probably very important for this process.

Time

UTC Thu 11-May-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee%20(CommComm)+Meeting+2017-05-11&iso=20170511T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+May+11%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1tysRywkgReTXtYlG_hSvxmbnV7V3dUoXei2v6uXiC0A/
• Previous Minutes Google Doc: https://docs.google.com/document/d/1YevHuA_csoTltDJ6mHr21fetZshNqWpsRbBRkSHhmYE/

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/board

• Clarify By-Laws WRT Community Committee #57

nodejs/community-committee

• Changed Collaborator to Member in README #49
• Documentation surrounding movement to/from TSC <> CC #47
• Request to move nodejs/education under CommComm #46
• Expanding the Node.js Collection: Reviewers #45
• Adding folks as members #38
• Moderation shortage #33
• Elect a Chairperson #30
• governance: who has voting rights? #21
• Add some scope (aka: stake your claim!) #13
• Central communication medium for chatting in Node.js #11

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Penny Hugger @pup (observer)
• Rachel White @rachelnicole (CommComm)
• Richard Littauer @RichardLitt (observer)
• Rod Vagg @rvagg (CommComm)
• Tierney Cyren @bnb (observer)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

Would love to get a "Good First Contribution" label added to the Community Committee repo by someone who has the privilege. I'm working on a draft of the contributing guide, and I'd love to be able to link to it as one of the items.

(Creating a new issue since it was indicated in #20 that anything pertaining to number of moderators would be considered off-topic there.)

I've noticed a shortage of moderation in #Node.js in the past few weeks, unfortunately. There have been a few cases where it was difficult to get hold of an active channel moderator, to deal with a problematic user - in fact, there's such a problematic user active in the channel right now that refuses to leave.

Is this a known issue?

Watch notes in real time! Ping us if you'd like us to broadcast from the Collab Summit.

• Minutes Google Doc:
  https://docs.google.com/document/d/1jR_dCInLb8_m-IScd0w57x-qUm3dvQxc2rYNNgPUGtU/edit?usp=sharing
• Previous Minutes Google Doc: https://docs.google.com/document/d/1YevHuA_csoTltDJ6mHr21fetZshNqWpsRbBRkSHhmYE/edit

Agenda

• What is a member?
• Flesh out communication channels for the project:
• Make an official, CoC compliant list of places we can send folks needing help!
• Document what problems we are trying to solve
• Update the cross-posted issue that we propose not to choose one over the other
• Can we create a hook from /help into IRC and/or Slack for people to get smaller help in realtime
• Moderation training
• Create a meta collaboration sessions at the fall Node Interactive, designed to get people new to the project who participated in, say, Code + Learn and then onboarding them into the various working groups participating in the collaborator summit.
• How do we go about bringing other communities into the Community Committee and Node.js Foundation?
• Is there such a thing as a roadmap for the Community Committee? What would that look like?
  Elect a Chairperson #30
  Collaborator's Summit agenda #28
  governance: who has voting rights? #21
• Add some scope (aka: stake your claim!) #13
• Central communication medium for chatting in Node.js #11

I'm going to voluntarily withdraw my (potential?) status as a voting member of the community committee. I will still certainly be involved in the discussions as appropriate, but given that there are already a couple of Node.js core participants here whom I trust implicitly, there's not much to be gained by me having voting status :-) ... it also saves me a bit of time (and guilt given that I haven't been able to make the meetings as of late). I am quite excited about the direction of the CommComm so far and hope it does quite well.

Just noticed that the Meeting Issue link was not added to the description of the second Hangouts On Air meeting. I know there was technical difficulty with getting it to go live, so I just wanted to ask if it could be added.

Video URL: https://www.youtube.com/watch?v=EOix1rU7s_Y
Meeting Issue URL: #62

So I've noticed that the Minutes are usually taken in Google Docs, and that there's only currently one markdown version of the Minutes in the /meetings folder.

At work, I've actually been using a small script I found online to convert Google Docs into Markdown files. I've put the script in a Gist (can't find the original source 🤔), and would be happy to help get people familiar with the workflow.

I'd also be happy to take on this responsibility myself, if that would be helpful!

I think that adding a section to the README.md file about the Community representatives, who are - as I understand it - representatives of the Community Committee to the Node.js Foundation Board, would be a good idea.

I imagine this would be in addition to the Community Committee members list. This also allows easy discovery and contact for the active Community representatives at any given time.

Fellow CommComm-ers: Managing the members of a GitHub Org has been a challenge. Soon we'll start adding sub groups around here and we'll want to manage the Teams.

The TSC recently closed my long standing issue to do this with a bot on there end. That's ok. I've kinda been on an island with my efforts. A bot was started that has been handling many other tasks, but not the ones I set out to do. I still believe this is the proper way to avoid burdening the TSC for these requests.

SO- I offer CommComm this: https://github.com/williamkapke/orgbot

It is purposely not specific to the Node.js GitHub Organization. My hope is that other Organizations could use it and it will gather more contributors focused on solving this problem.

This is only an offering. We can choose to go a different route. BUT,I'm just happy that I finally have this solution out there so we can no longer say "IF we had a bot for this" 😄

I have it running on my test Org. If you would like to play around with it, just let me know and I'll add you to the Org!

Let me know your thoughts. If positive, we'll pursue putting this in production.

It's been quite a long story with One-Shot, NodeConf and Node conferences around the world, so I'd like to bring up this discussion again without looking too much into the past.

From my perspective, NodeConf organisers are individuals standing up and making a huge effort for Node.js and, having a NodeConf working group would be recognising that effort within he foundation.

As a founder and co-organiser of NodeConf Barcelona I'd like to help others to run a NodeConf in their city and maybe build up a Node.js User Group together with NodeConf. We could share experiences and build up a network (of sponsors, attendees etc.) to build up a global NodeConf brand.

What are your thoughts?

over the past few month, the CommComm has been debating the relative merits of several communication channels for the Node.js project: #11

a key issue yet to be fully addressed is the need for active moderators and helpers in whatever channel(s) we end up choosing. this is critical as the tool(s) we choose need to work for the people who plan on staffing them.

to that end, this is an open call for people interested in volunteering to moderate and help in these channels. general tasks are:

• enforce Node.js CoC by calling out behaviors, educating users on better behaviors
• offer Node.js guidance, by pointing to resources or otherwise

if you are interested, please indicate your interest with details/restrictions you have below.

cc @emilyrose @aredridel @nodejs/tsc

there is a long tradition of fantastic moderation in the Node.js IRC that i hope we can learn much from as we move forward.

Now that I better understand the scope from reading the last minutes, I'd like to at least listen in.

It was brought to my attention, for good reason, that we don't have a really obvious path for people to become 'members'.

Some suggestions for highlighting folks:

• activity in this committee
• activity in the org the person is attending to represent(OSS project, event such as NodeSchool, etc)

Questions to consider for the movement to be added:
I've seen other groups require nomination, but I think this can be really intimidating or take too long a proving time for some(or be a bit political for others, which, let's not do that).

• Can we encourage self-nomination?
• Would a private form help so people don't feel like they are having to 'prove' themselves out in the open?
• Can we start folks off as observers as they request and then set short timelines(maybe including an actual calendar date) for them to be added as members?

The TSC went through a long process of deciding what its scope is. I'd post reference links here... but it spanned so many issues & PRs- it's too much to follow.

This was the final solution: https://github.com/nodejs/TSC/pull/144/files

In it, we decided it was appropriate to define what repo's were within the TSC's domain. There are a few in there that may belong to the CC, so take a look and lets discuss.

Here are the ones I have my eye on:
https://github.com/nodejs/code-and-learn
https://github.com/nodejs/education
https://github.com/nodejs/help
https://github.com/nodejs/summit
https://github.com/nodejs/evangelism (whether to move Evangelism under CC is a new topic)
https://github.com/nodejs/inclusivity (def lots to discuss on this still)
https://github.com/nodejs/inclusivity-slack-inviter
https://github.com/nodejs/live.nodejs.org
https://github.com/nodejs/moderation (private.. well except to >500 people in the org)
https://github.com/nodejs/members

Obviously, https://github.com/nodejs/community-committee should be.

Having "under the CC's scope" doesn't mean the CC needs to do much. It's just the body of people that things could bubble up to if needed. For instance, if help was under CC.. the CC would get pinged when someone wants/needs people added to the help team. Or, sometimes a README needs to be updated and no one has commit access to the repo-- this would delegate it to the CC to go hit the Merge button.

I don't believe I'm 100% correct on this list... it's just some suggestions.

It's not clear to me who has voting rights on the CC (e.g. for purposes of bringing on a new member) - is it all members or only advisors?

I thought it would be helpful to create an issue to track what's still needed to get CommComm chartered by the board. It's probably too late to get any updates before the board meeting next Monday, but maybe we could target having an updated revision to present at the meeting after that?

My understanding is that there was some feedback from the board in a previous meeting, and that we still need to update the charter with that feedback. Is that correct @hackygolucky?

Time

UTC Thu 13-Apr-2017 20:00 (08:00 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation++Meeting+2017-04-13&iso=20170413T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Apr+13%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/18d2XeUP_dB4dyLzjO6wqs6NiaSaUxLFDyXYL_HFTEDc/edit?usp=sharing
• Previous Minutes Google Doc: N/A (first meeting!)

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/community-committee

• Elect a Chairperson #30
• Collaborator's Summit agenda #28
• governance: who has voting rights? #21
• Add some scope (aka: stake your claim!) #13
• Central communication medium for chatting in Node.js #11

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• James Snell @jasnell (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Rachel White @rachelnicole (CommComm)
• Rod Vagg @rvagg (CommComm)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

After discussion, there is interest in exploring a self-hosted IRC server setup. Self-hosting allows us to implement monitoring, logging, and authentication models that enable the kind of IRC community we want to grow.

The first step is to create a small-scale prototype to get a closer understanding of the effort and logistics involved in a self-hosted IRC server with these qualities. This prototype does not need to be scaleable or production-grade, but it should showcase the features we want.

Here is a non-exhaustive list of the features I think we should have (feedback requested):

• Authentication and login using GitHub to simplify the login experience
• A web client that user's automatically get logged in to, along with a way of making this optional for folks that want to use a different client
• Logging/auditing of all messages, along with time-limited storage of logs/audits.

A great opportunity for someone wanted to get some pull requests in Node.js. Per these issues, nodejs/TSC#224 (comment) and #7, Node.js is trying to consolidate the CoC into one place so that when it is updated, it is updated across all places it's been referenced instead of copy/pasted.

So, other versions meant to be representing the source CoC should be replaced as links pointing to The Code of Conduct.

Was reviewing and noticed that there were two places where a Code of Conduct is stated - one in the COLLABORATOR_GUIDE.md file and one in the CODE_OF_CONDUCT.md file.

I read a bit of the two, and they vary slightly. To ensure that there is no confusion or pointing to an incorrect Code of Conduct, should we update the Code of Conduct to be the same in both places?

Since the CODE_OF_CONDUCT.md file seems to be more detailed, I'm guessing that's the intended primary Code of Conduct.

Per the Charter, CommComm gets to elect a Chairperson.

The CC will elect from amongst voting CC members a CC Chairperson to work on building an agenda for CC meetings and collaborate with the Individual Membership Directors the wishes of the CC to the Board for a term of one year according to the Node.js Foundation’s By-laws. The CC shall hold annual elections to select a CC Chairperson; there are no limits on the number of terms a CC Chairperson may serve.

We do not have a predefined process for this - let's get that figured out!
(e.g.: Nominations open for 1 week, voting open 1 week)

Meeting 2017-06-22 Community Committee (CommComm)

Time

UTC Thu 22-Jun-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation++Meeting+2017-06-22&iso=20170622T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+22%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1GXbfPhfbLTr7g9Hp7YP-M60ux_Ua2z8XRXg__me4u4k/
• Previous Minutes Google Doc: https://docs.google.com/document/d/14Pd6e40n1wPEuRBknDJUFwlf9XDhWI94jCgMEvTfVS4/

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/community-committee

• Adding Jenn and Tierny as members #77
• Move Node Together Repo as an org under CommComm #63
• Request to move nodejs/education under CommComm #46
• Adding folks as members #38

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Olivia Hugger @pup (observer)
• Rachel White @rachelnicole (CommComm)
• Richard Littauer @RichardLitt (observer)
• Rod Vagg @rvagg (CommComm)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)
• Michelle Garrett (msmichellegar) (CommComm)
• Micheal Dawson @mhdawson (observer)
• Tierney Cyren @bnb (observer)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/tsc members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

The process of nominating yourself is somewhat problematic. Once 1 person has run, all others that run after imply a negative statement. Such as: I think I could do better than the others or I think the others are wrong. I'm sure, in some cases, those types of statements are intended.

The scenario has similar implications when a person nominates another person.

In politics- these confrontations are on the front lines of the debates- but in an organization that wants to promote an encouraging/welcoming environment, this is not optimal. Conflicting opinions are not a terrible thing for some things (like technical decisions)- but when it relates to an individual's personal performance- it creates an uncomfortable environment/scenario.

I'm confident that many studies have been done on this; SO... does anyone know of an existing process/framework for a non-confrontational way to run for elected positions?

I would like to review some existing concepts before trying to create/discuss our own.

Currently, the Education repo for Node.js is floating in lalaland, unchartered. I'd like to officially move this under CommComm scope.

Since there wasn't a charter and there hasn't really been involvement from @nodejs/tsc from generally, things in the Node.js org fall under their scope, do I need to ask the TSC to move this? Otherwise, I request the CommComm votes on this in the next meeting.

Request to TSC here.

A few members of the evangelism working group recently reached out the the Node.js Foundation communications team to figure out how we could work together to incorporate more community-generated content across Node.js Foundation social channels.

We decided a great option for this would be to create a Node.js Medium publication. In addition to working closely with representatives from the EWG, we also worked with @hackygolucky to come up with a plan to address this.

We plan to launch this publication tomorrow; it will be titled The Node.js Collection. I will share the link once it's live.

Below are our overall goals for the publication, what we are looking for in submissions and how to submit. A key goal of ours is to showcase content that reflects the ever-expanding diversity of ideas, innovation and voices within the Node.js community. Any efforts this group can lend to help encourage a range of submissions from all corners of the community and globe are greatly appreciated.

Purpose of Node.js Foundation Medium publication
The Node.js Foundation’s new Medium publication serves as a channel for the community to broadcast to a wide audience its views related to Node.js and its ecosystem. This may include:
-Summaries of incubated projects or technical decisions made
-Working project initiatives
-Use cases and success stories
-Industry insights and best practices around Node.js and development trends (see topic areas below)
-Reports on Node.js and JavaScript events (these events must have a code of conduct to be considered)
-Other topics will certainly be considered, but it should be something of interest to the Node.js community

Quality
We are looking for posts that teach and provide value to our community. Contributions should include the meta-narrative that “Node.js is maturing and gaining widespread use in mainstream enterprises, while continuing to inspire amazing potential and creativity among the massive community using the platform.”
Sub-domains and topics for the Medium page include:
-Serverless/Cloud
-Containers
-Community
-Best Practices (How To)
-Embedded/IoT
-AI/Mobile
-More (Essentially news from the Foundation and potentially more editorial style content about the future of Node.js Core) - see Google Cloud Platform’s More section as an example here.

Guidelines/General Tips of Submissions
Posts from members and community members must be vendor neutral, though they may mention vendors involved in specific project deployments if this serves the purpose of educating readers.
Posts about hosting of an in-person event or speaking at an event, or other indications of meaningful participation in the community, are allowed, but again shouldn’t feel like an advertisement for your services or company.

Your post must be your original content, but can be published on the Node.js Foundation Medium publication, if you received permission from the editors of the website to do so.

All content should have a byline (preferably by a company engineer) and be published with Creative Commons with Attribution, so you’re welcome to republish on your blog.

The most interesting posts are ones that teach or explain how to do something in a way maybe others haven’t thought of. Good blog posts show hurdles that were encountered and explain how they were overcome (not that everything is rainbows and unicorns).

A few posts that have performed well on the Node.js Foundation Medium page include Walmart Strives to be an Online Retailer with Node.js (use case); Node.js Transitions to LTS (news); The Progress of Node.js Post io.js and Node.js merger (progress update).

When showing upstreaming of a patch fixing an issue for others, link back to the Github issue so readers can follow along. We don’t avoid critical commentary or broad issues, but approach them with sensitivity, professionalism and tact in a way that is beneficial and positive for the community. Node.js Foundation Medium posts should be no longer than 1,000 words and no shorter than 300 words.
Diagrams or photos are strongly encouraged.

How to submit for consideration
Please submit a brief summary and the topic of the post to [email protected] for consideration. The email alias reaches the review team consisting of Zibby Keaton, Sarah Conway, Tracy Hinds, Mikeal Rogers, Tierney Coren, Ross Kukulinski (with the potential to expand in the future).

Members of the Node.js Evangelism Working Group and Node.js Foundation PR team will review your submission in an a timely manner and provide the green light to draft the entire article or provide feedback or direction.

If you are submitting an article or presentation that already exists, please send it in its entirety with a note on the expressed permission to publish from the owner of content.

Once your submission has been approved, it will be added to the Node.js Foundation Medium publication publishing calendar and a publish date will be provided, so you may plan to promote accordingly through your personal and company’s social media channels.

Review Process for Original Posts
The review team will provide comments and edits. Once the review team has made suggested edits, the post will be shared with the full evangelism working group, which will be given three days to provide additional edits/comments.

The review team will share all suggested edits with the author, who has final sign off on content. Zibby Keaton will then post to the Node.js Foundation Medium publication. The review process may take between two to three weeks depending on the number of edits and revisions involved.

Review Process for Created Medium Posts
-Members from the evangelism working group are invited to become editors on Medium. If interested, contact Zibby Keaton here: [email protected].
-Editors are allowed to request to put already available public content on the Node.js Foundation Medium publication if they follow the above guidelines.

We've had some really excellent discussions in #11 surrounding how we can improve our community's central chat space(and really what -that- is).

An interesting question brought to me was how we DO finally decide this. I can't make that call and won't(not how the world works!). A simple vote by majority may not necessarily represent what will set us up for success. It's possible the volume of people voting may not have struggled with each of the mediums, the logistics of moderating them, and the problems with onboarding new folks to either. I find that weighing collaborators/moderators of IRC(or Slack if there are any currently)/community-at-large as separate votes may help us figure out the final call.

To get the feedback we need for folks to work together on this, I propose we run votes for the three separate votes for the various stakeholders here:

1. contributors
2. community members
3. existing moderators

To do this, I think we need to iron out the logistics of voting. Does @nodejs/tsc have any precedence with doing something like this? Collaboration on this would be really appreciated and very helpful.

Now that we have been officially chartered, should we start holding regular meetings like the TSC does? I think it would be helpful in generating momentum, at least at the beginning.

Meeting 2017-05-25 Community Committee (CommComm)

Time

UTC Thu 25-May-2017 20:30 (08:30 PM):

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation++Meeting+2017-05-25&iso=20170525T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+May+25%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1J14T5lXuFWsaTqfkpmPruAZ4E-WsVe2V5TAaKwDjHN0/
• Previous Minutes Google Doc: https://docs.google.com/document/d/1tysRywkgReTXtYlG_hSvxmbnV7V3dUoXei2v6uXiC0A/

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/TSC

• Request to move moderation responsibilities to CommComm #270

nodejs/community-committee

• Charter tweaks #50
• Expanding the Node.js Collection: Reviewers #45
• Adding folks as members #38
• Moderation shortage #33

Invited

• Ashley Williams @ashleygwilliams (CommComm)
• Bryan Hughes @nebrius (CommComm)
• Emily Rose @emilyrose (CommComm)
• Gregor Martynus @gr2m (CommComm)
• Jenn Turner @renrutnnej (observer)
• JP Wesselink @jpwesselink (CommComm)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Myles Borins @MylesBorins (CommComm)
• Penny Hugger @pup (observer)
• Rachel White @rachelnicole (CommComm)
• Richard Littauer @RichardLitt (observer)
• Rod Vagg @rvagg (CommComm)
• Sarah Conway @SarahKConway (observer/Node.js Collection)
• Tierney Cyren @bnb (observer)
• Tracy Hinds @hackygolucky (CommComm)
• William Kapke @williamkapke (CommComm)
• Zibby Keaton @ZibbyKeaton (observer/Node.js Collection)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/tsc members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live 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 & streaming. So be patient and it should show up.

Looking through the Collaborator's Guide a bit, I noticed two references to the "website project" and several references to code contributions (like that executable code needs to run through the CI process).

I'm guessing this was a simple C&P from the website's Collaborator Guide with edits , and these parts were simply missed. 😊

Someone just asked in the Education repo (nodejs/education#31) if they could start a meetup at their school. I absolutely love the initiative and thought here, and would like to see if there's some kind of document we could pull together with resources that are ready-to-use like NodeSchool.

I've had a hard time with NodeSchool myself, but that's because I've always gone solo - would be great to pull similar resources, groups, and efforts into a One Page that can be easily consumed and shared.

Hi folks! I think most of you are already aware, but Evangelism has expressed interest in moving to CommComm.

We're still waiting on official signoff, but it looks like we have consensus from both the Evangelism WG and the CTC, who currently oversees the WG.

Are there any objections from @nodejs/community-committee to moving Evangelism under CommComm?

We have a moderation escalation policy in place, but it is untested, unused, and pretty light on details. More specifically, it's not well suited to handling conflicts between people in more "leadership" roles (as much as we have leaders in this project).

We should do some research to see what best practices are for handling moderation escalations and how other projects are tackling this problem. Then, let's come up with a policy proposal and submit a PR to the moderation policy in the TSC repo.

Just a quick question – is the @nodejs/community-committee team member list correct? If it should match the list of people in the readme, it’s outdated and should be updated (happy to do that myself if that’s the case). If not, I don’t quite understand the difference between the two groups (?).

As part of the strategy to improve inclusivity in Node.js, it was proposed to create a more central, discoverable communication medium for Node.js.

See improving our central communication channels discussed here at Node Interactive

Thoughts on the comparison:

(1) Revitalizing and cleaning up the IRC community.

• Publish list of channels with webchat link to them on nodejs.org under ‘Get involved’
• All published channels would be those who have agreed to adhere to the Node.js CoC and will list it as a topic in the channel
• Require logging for reporting of issues to moderation
• Outreach effort to encourage positive community and conversational energy to IRC, as many of these conversations have fled to Slack organizations that can be difficult to discover or get into.
• For this option to work, the moderation policies in current existence for IRC would need to be refactored and pull requested into the nodejs organization as part of a guide for the Code of Conduct. The current policy does not handle online, year-round communities comprehensively.

OR

(2) Creating a new, central Node.js Foundation Slack organization

• Open by default--We will set up an open sign-up to allow for anyone who would like to participate in the Slack to do so. This sign-up also allows us to gate participation in the community ONLY by requiring participants to agree to adhering to the Code of Conduct.
• unpaid Slack org with IRC bridge enabled. Other non-profits we've talked to that have as large of a userbase as us and have tried have run into exponential cost increases, even with the severe non-profit discount Slack provides upon application. A suggestion was made for alternative logging(can be used via an IRC bridge/logging)
• General, random, and working group-ish channels(could have private ones for discussions needing to be protected with a policy of keeping convos pointed to public channels as much as possible)
• Allows for the ability to moderate with admins easily--all channels can be seen and in instances of reporting for violations, there is a log.
• Since sign-up is required, it can be more difficult for abusers to cloak themselves under another name and continue to be toxic in a community that is gated.

I would love to hear comments below about the pros and cons of each! But voting is really helpful here.

If you'd like to vote, the Emoji reaction survey system is this:

React with
😄 === IRC 'refactor'
🎉 === Central Slack org

cc @nodejs/tsc @nodejs/ctc @nodejs/evangelism