-
Notifications
You must be signed in to change notification settings - Fork 70
Conversation
I think we should not make assumptions on how versed folks are with 1. Open source practices and 2. Node.js project practices for interacting and administrative duties related to our work, since many of the contributions for our work can live outside of the GitHub project workspace. |
To not make assumptions about the familiarity level of people with Node.js project and open source practices, the guide should contain some starter info. Addresses: #342 (comment)
Agreed ^^ Added some material to start. |
@chowdhurian @hackygolucky any thoughts on adding a small section about the "consensus seeking" model? |
It's the cornerstone of the process here, crucial to buy-in and cooperation. Added! |
should process around becoming a members get added in this document? |
@codeekage nope, that belongs in other documentation. The explicit goal of this is to ensure that once we do accept a new member, that we have a laid out process to follow. |
This document looks good overall to me. I think a helpful process to call out is the minimum amount of time required for review before we can merge a document. It isn't consistent across the project, so making sure it is known would be nice here. This whole section is particularly helpful to mention but the hours specifically
We can discuss whether it should be consistent across the project in another issue :) |
Copy/pasted that section @hackygolucky 👍 Going to land this. Let's iterate from here on! 🎊 |
Created a quick initial document for on-boarding new CommComm members. Wanted to throw something together so we can begin discussing and building upon it 👍