Closed ghost closed 6 years ago
I'm in! Thanks for the hard work of everyone in the meeting prior.
Will be there!
@oe added to the Node.js Calendar 👍
I'd like to attend but I will be out of the office that day so I'll probably miss it.
One thing I'd like to suggest for discussion is the introduction of "collaborators" for CommComm. I know we can't necessarily make the criteria commits, but just like the technical side it can be from contributions being made which just need to be outlined in the nomination.
This would at least solve a few current problems:
It also provides a path that supports scaling more easily, initial contributor -> collaborator -> CommComm member.
With the members typically being the most active collaborators (at least that is commonly the case on the technical side). At this point I'd still keep it so that anybody can join the CommComm meetings as an observer, but work to push actual work into working groups so that over time that is where the real action is.
@mhdawson I'm really glad you brought this up, this is very much along the lines of what @oe and @Tiriel were discussing in the prior meeting. I'm definitely +1 as well, and I think putting definition to what a "Collaborator" is will be wholly beneficial for the CommComm overall.
Aye, that's definitely something along the lines of what I was proposing at first, with the complementary step that new members should actively championning or at least participating in a WG or an initiative.
So that's a +1 for me, and I definitely think this is worth discussing in the next restructuring meeting!
Meeting Notes are here: https://docs.google.com/document/d/1mlk48QmZcGCyJHVRCj_ZorHN3BX_xncQZ5tR-Hvsz6M/edit?usp=sharing
Link to join the meeting: https://zoom.us/j/150571995
Heyo! Following up from last meeting, we had another work session on the calendar for today, but I don't think we had anyone scheduled to lead it. Should we propose a time for next week or the week after to continue this work?
Would the same time next week work? If so, I'll make an issue for it.
Damn, completely had forgotten too. Sometimes next week would definitely be better for me!
@chowdhurian that would work for me. I suggest creating an issue and proposing the time but being open to it changing 😄
Closing this, as a new issue has been opened for the next meeting to continue the Restructuring Efforts
Continuation of #234.
Meeting time: 13th of March 2018, 6:00PM UTC
Previous minutes: https://docs.google.com/document/d/1jVUmEId-McK8Aooenwfm8gDjsaAbisiLDMjQ9PsyYlA/edit?usp=sharing
Local time: https://docs.google.com/document/d/1jVUmEId-McK8Aooenwfm8gDjsaAbisiLDMjQ9PsyYlA/edit?usp=sharing
Invited: @nodejs/community-committee