-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: Review CommComm Charter Update #383
Comments
Update: I've addressed all outstanding comments and requested changes ❤️ |
+1 from me. |
I've approved this in the Community Committee, but here is my explicit LGTM here on this issue. |
+1 LGTM |
LGTM since this removes references from the board it might be good for an FYI to the board before landing. |
Sent FYI to the board on 11/18/2019, asked for any concerns to be sent to me before the end of the week. |
No comment/issues from the board, believe we are good to go once approved by the CPC |
+1 from me. |
Based on the requirements for approving charter changes (see https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#aproving-project-charters) I think this is ready to land. (2 voting members that approved @joesepi, @kborchers) |
Merged. Thanks y'all 🎊 |
Over the past few weeks, the Node.js Community Committee had built out and refined updates to our charter that reflect the Node.js project’s existence in the OpenJS Foundation rather than the Node.js Foundation.
We seem to have come to consensus with no objections, per our normal decision making processes. If there are any outstanding comments in it, I will resolve them prior to the next CPC meeting (PR rendering on mobile isn’t perfect).
Reference: nodejs/community-committee#526
The text was updated successfully, but these errors were encountered: