-
Notifications
You must be signed in to change notification settings - Fork 134
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
Re-charter the Ecosystem Security WG #1081
Comments
Thanks for opening the issue. For context for others: This is referring to the Ecosystem Security WG. The charter mentions Node.js Foundation but that foundation doesn't exist anymore. In #1053, it's changed to OpenJS Foundation. I'm not 100% sure that's correct. If it is correct, then the charter needs to be updated too. If it's not correct, then both the charter and WORKING_GROUPS.md need to be updated. |
I think we could think of de-chartering it given the ecosystem program was halted? |
@mcollina @MylesBorins had suggested in this previously and after I mentioned we should talk to @lirantal and @esarafianou first as the most active members. I think @MylesBorins had said he was going to do that. EDIT: We do need a change either to change the chartered scope or to de-charter. |
@nodejs/security-wg TSC is trying to figure out if we need to update your charter or simply de-charter you and let you folks continue to work as a GitHub team rather than a chartered working group. I'm not sure that there are relevant advantages to being a working group. Your feedback would be great. I've added the |
@Trott Could you elaborate what are the differences between those charters (if there is a document explaining it would be awesome)? Currently, the group is working pretty similar to any other working group. We have bi-weekly meetings, initiatives... |
A chartered working group is formally delegated responsibility, while a team simply is a group of people working in an area without any formally delegated responsibility. Pratically there is little difference day to day. |
We discussed today in the security-wg team meeting. The consensus was that for the current work we don't need a formally chartered team. Our understanding is that we can continue in the same way we have (with repo, team etc.) if the wg is de-charted. In that context we are ok with decharting the WG. |
@Trott FYI |
It seems that the working group can function as a GitHub team. Closes: #1081
It seems that the working group can function as a GitHub team. Closes: #1081
* decharter Ecosystem Security Working Group It seems that the working group can function as a GitHub team. Closes: #1081 * fixup! decharter Ecosystem Security Working Group
In relation to "Node.js Foundation technical group"
We should probably re-charter the group with that removed too.
Originally posted by @Trott in #1053 (comment)
The text was updated successfully, but these errors were encountered: