-
Notifications
You must be signed in to change notification settings - Fork 56
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
TAC: Define blog post pre-publication review process for GB/TAC #42
Comments
Hello. As part of 2022 backlog grooming, each open TAC issue is being reviewed for applicability/completeness. Has this request been completed? If so, can that be noted in a comment please. If not, what actions need taken to continue moving this issue to completion? Is this an item that the TAC needs to address in 2022? If we do not here back from you within two weeks, this issue will be closed (23March2022). Thank you. |
@jorydotcom this appears to be something that needs included in your documentation/process scope |
@jennbly do we have docs written up for this? If not, could we get a short process scribbled out to guide us? Thanks! |
@SecurityCRob We have our content policy here: https://github.com/ossf/foundation/blob/main/OpenSSF%20Content%20Policy.md |
woot woot! |
Ongoing discussion on the openssf-gb and openssf-tac mailing lists. I am coordinating feedback in-thread on a proposal created for how this will work.
The text was updated successfully, but these errors were encountered: