This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #199 from nodejs/bnb/meeting-minutes-2017-12-14
Adding meeting minutes for 2017-12-14
- Loading branch information
Showing
1 changed file
with
95 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,95 @@ | ||
| # Node.js Foundation Community Committee (CommComm) Meeting 2017-12-14 | ||
|
|
||
| ## Links | ||
|
|
||
| * **Recording**: https://www.youtube.com/watch?v=KBl89HF4Qpk | ||
| * **GitHub Issue:** #192 | ||
| * **Minutes Google Doc:** https://docs.google.com/document/d/1t2mseYq8-EKlxMiluHq2k2s8qh7bIX0nIEJb8QiSFH4/edit?usp=sharing | ||
| * **Previous Minutes Google Doc:** https://docs.google.com/document/d/1SWJjGXEpTdu_2RbUkHr05h3WZco3pFrq59p4gDoKTnc/edit | ||
|
|
||
| ## Present | ||
|
|
||
| * Adam Miller (@amiller-gh) | ||
| * Michael Dawson (@mhdawson) | ||
| * Ben Michel @obensource | ||
| * Ahmad Bamieh @Bamieh | ||
| * Diego Zoracky @DiegoZoracKy | ||
| * Dan Shaw @dshaw | ||
| * William Kapke @williamkapke | ||
| * Joe Sepi @joesepi | ||
| * Toby Farley @tobyfarley | ||
| * Sarah Conway | ||
| * Manil Chowdhury @chowdhurian | ||
| * Tierney Cyren @bnb | ||
|
|
||
| ## Notes | ||
|
|
||
| Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting. | ||
| Extracted from **cc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
|
||
| * Mentorship Team under the CommComm #172 | ||
| * Node.js Strategic Initiatives beyond technical matters #186 | ||
| * Node.js People Everywhere (npe) #184 | ||
|
|
||
| ### User Feedback update | ||
|
|
||
| * Had first meeting | ||
| * Regular interval set for every 2 weeks | ||
| * Next meeting Greg from Linux foundation will give us some additional insight on the yearly | ||
| Node.js survey, discussed having people opt in as part of the survey as being interested in | ||
| being contacted for additional questions etc. | ||
| * Issue asking for business involvement - https://github.com/nodejs/user-feedback/issues/20. | ||
| Adam volunteered to make an email template people can use to forward to companies they | ||
| think would be good to invite and add to issue. | ||
|
|
||
| ### Mentorship Team under the CommComm [172](https://github.com/nodejs/community-committee/issues/172) | ||
| * Goal is help more people join the community | ||
| * Working in https://github.com/Bamieh/node-ment | ||
| * Will be sending pairs that they match an email | ||
| * Have meeting with pair to do introductions, setup communication channel and how to go | ||
| Forward | ||
| * Matching should come from the repos (ex core should nominate mentors/mentees for | ||
| that repo) | ||
| * Pairing done by commcomm participants. | ||
| * Factor in language preferences | ||
| * Add info to repo README as well as have slack to communicate | ||
| * Restrict mentorship to a given timeline, suggested 6 months is a good timeline which | ||
| gives around 10-12 meetings. | ||
|
|
||
| * TODO: Tierney volunteered to open issue in Admin to propose moving repo into the nodejs org | ||
| * TODO: issue in TSC for awareness - https://github.com/nodejs/TSC/issues/443 | ||
|
|
||
| ### Node.js Strategic Initiatives beyond technical matters [186](https://github.com/nodejs/community-committee/issues/186) | ||
| * Discussion on. LinkedIn discussion, reasonably large membership base, currently owned by member of the | ||
| Foundation. https://github.com/nodejs/evangelism/tree/master/documents/local_initiatives | ||
| https://github.com/nodejs/community-committee/issues/185. Discussion about getting foundation/community committee | ||
| * In agreement that we should do it (no objections). | ||
|
|
||
| ### Node.js People Everywhere [184](https://github.com/nodejs/community-committee/issues/184) | ||
| * Diego gave us a quick overview | ||
| * suggestion for platform/website to help companies and people get together | ||
| * this will help build community by making companies more comfortable that they can get resources | ||
| they need if they chose Node.js and developers find companies if they want to work with Node.js | ||
| * would be good as pages on main website or at least very closely linked | ||
| * some good examples of other places doing something along these lines: | ||
| * https://github.com/remoteintech/remote-jobs | ||
| * http://www.scala-lang.org/community/ | ||
| * Tierney - example were we had allowed submissions of local events: | ||
| https://github.com/nodejs/evangelism/tree/master/documents/local_initiatives | ||
|
|
||
| * Next steps | ||
| * TODO: Diego: figure out what MVP looks like in the issue | ||
| * TODO: Tierney: find additional contributors | ||
| * TODO: Tierney: find champion in community committee and then add to initiatives list | ||
|
|
||
| ## Q&A | ||
|
|
||
| * should I know html and css before starting Node.js ? | ||
| * repo nodejs/help good place to start | ||
|
|
||
| ## Upcoming Meetings | ||
|
|
||
| * **Node.js Foundation Calendar**: https://nodejs.org/calendar | ||
|
|
||
| Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. | ||
|
|