-
Notifications
You must be signed in to change notification settings - Fork 40
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
WG Charter updates #52
Comments
Upstream issue needs to be resolved: ossf/wg-securing-software-repos#4 |
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). |
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. |
Charter has been updated and merged into repo. |
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) - ossf/tac#9
(2) - https://github.com/ossf/wg-security-tooling/blob/main/CHARTER.md
The text was updated successfully, but these errors were encountered: