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
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.
@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 security-wg-agenda label to this, but feel free to remove, of course.
@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.
Activity
Trott commentedon Sep 2, 2021
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.
mcollina commentedon Sep 7, 2021
I think we could think of de-chartering it given the ecosystem program was halted?
mhdawson commentedon Sep 8, 2021
@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.
[-]We should probably re-charter the group with that removed too.[/-][+]Re-charter the Ecosystem Security WG[/+]Trott commentedon Sep 28, 2022
@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
security-wg-agendalabel to this, but feel free to remove, of course.RafaelGSS commentedon Sep 28, 2022
@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...
mhdawson commentedon Sep 28, 2022
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.
mhdawson commentedon Oct 27, 2022
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.
mhdawson commentedon Oct 27, 2022
@Trott FYI
decharter Ecosystem Security Working Group
decharter Ecosystem Security Working Group
decharter Ecosystem Security Working Group (#1351)