-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create on-call runbook/playbook #23
Comments
Started to address "What are the expectations for on-call?" in new section On-Call Duties section on our "For working group members" Confluence page. |
Added runbook on finding a maintainer in our Security Playbooks. |
Started draft sections: Added to Triage [email protected] emails. |
Added section Forward a report to an operator or Axim. |
@alangsto & I met and compiled the current 2U practices. We now need to compare them. |
@alangsto & I met and added details to Security Playbooks – for Security WG members. |
@feanil & I met and we worked on Common Issues. |
We need a runbook so it's clear to working group members how to respond to security disclosures.
Some open questions from: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3624140816/Security+Working+Group+Private:
The text was updated successfully, but these errors were encountered: