You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
This is the primary issue tracking conversation around the desire to document and describe how the core team for Node.js should operate. Be that in terms of governance, structure of members, and resources.
All issues should be tagged with the CoreTeamWorkingGroup label, and you can find the list of those issues here
CoreTeamWorkingGroup
Use this issue for conversations about the Core Team Working Group itself, who the members are, and what it's output is expected to be.
Initial issues and topics were bootstrapped from an internal advisory board email thread.
The text was updated successfully, but these errors were encountered:
Before attempting to comment on these issues I realized that most of them require prior knowledge of the governance model that Node Forward adopted. Furthermore, I think it would help if there was documentation on a model that we can reference and make modifications to. And so, I've adapted the Node Forward model for use in this discussion #11
This should make it easier to document and iterate on a model that can be discussed and potentially adopted at the next Advisory Board meeting.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is the primary issue tracking conversation around the desire to document and describe how the core team for Node.js should operate. Be that in terms of governance, structure of members, and resources.
All issues should be tagged with the
CoreTeamWorkingGroup
label, and you can find the list of those issues here CoreTeamWorkingGroupUse this issue for conversations about the Core Team Working Group itself, who the members are, and what it's output is expected to be.
Initial issues and topics were bootstrapped from an internal advisory board email thread.
The text was updated successfully, but these errors were encountered: