search

ossf / wg-securing-critical-projects

Helping allocate resources to secure the critical open source projects we all depend on.
Apache License 2.0
331 stars 40 forks source link

WG Charter updates #52

Closed SecurityCRob closed 1 year ago

SecurityCRob commented 2 years ago

Hi. The OSSF TAC is seeking to get an issue(1) closed out. We want to ensure all working groups have a complete charter.md file and as I reviewed this group's file I noticed that this WG does not have a charter in place. The Tooling WG has the best example of what we'd like to see(2), it can be copied and adjusted for this WG. Can you please make a copy, review with the WG, adjust as needed, and post it into your repo? Thank you for your assistance in this matter.

(1) - https://github.com/ossf/tac/issues/9 (2) - https://github.com/ossf/wg-security-tooling/blob/main/CHARTER.md

jeffmendoza commented 2 years ago

Upstream issue needs to be resolved: https://github.com/ossf/wg-securing-software-repos/pull/4

jeffmendoza commented 2 years ago

https://github.com/ossf/project-template/issues/4

jeffmendoza commented 2 years ago

After discussion in the WG meeting today. We will wait for further wordsmithing on the template (linked above). Then we'll customize it with a pointer to our goal (https://github.com/ossf/wg-securing-critical-projects#focus) and leads (co-chairs).

christo4ferris commented 2 years ago

Seems to me that we are left hanging with the tacit agreement to remove the confusing language, I see no reason that this issue cannot be closed by adopting the current template and updating once the TAC has made the change, or alternatively remove the section as @jchestershopify has done in his fork.

Amir-Montazery commented 1 year ago

Charter has been updated and merged into repo.