-
Notifications
You must be signed in to change notification settings - Fork 152
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
Standardize on Collab Spaces over Working Groups #1110
Comments
The concept of working groups as inherited from the Node.js project makes less sense to me in the context of the foundation. I'd favor consolidating into Collab Spaces. |
This doesn't seem so bad to fix: No bylaws impact. Just a single mention of WGs in the charter. The only question is want we want to do with the authority delegation aspect of WGs. For the record, the CPC delegates a scoped decision-making power to the WG via the WG's charter. A WG is able to represent the Foundation in that context. That is not currently the case for Collab Spaces. IMHO, this power delegation is important in some cases, for example, to allow WG members to represent the Foundation in standard bodies, so we need to keep it around. I think we can just specify in the Collab Space's charter whether or not the CPC delegates decision-making power to the Collab Space (and what exactly is delegated if that's the case). We'd just need to amend the docs accordingly and update existing Collab Space charters to be specific that there isn't any delegation going on for them. [Edit: task list moved to the top of the issue.] |
are there any objections from anyone on the @openjs-foundation/cpc to simplify and standardize on collab spaces? in today's meeting, we had no objections and would like to move forward on the work. |
Lets make sure to alert @openjs-foundation/standards if they haven't been already. |
Beat you to it: openjs-foundation/standards#253 |
Meeting notes:
|
We have Collab Spaces and Working Groups. I don't think we need both and I've heard from multiple people that having both is confusing.
Related: #1108
There's agreement to move forward with this. Here are the steps:
The text was updated successfully, but these errors were encountered: