Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Core Team Working Group Tracking Issue #5

Open
tjfontaine opened this issue Nov 14, 2014 · 1 comment
Open

Core Team Working Group Tracking Issue #5

tjfontaine opened this issue Nov 14, 2014 · 1 comment

Comments

@tjfontaine
Copy link
Contributor

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.

@mikeal
Copy link
Contributor

mikeal commented Nov 14, 2014

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants