From 7577df2f395da634326d90fff573777489fb9c35 Mon Sep 17 00:00:00 2001 From: Sebastian Beltran Date: Mon, 9 Dec 2024 17:47:27 -0500 Subject: [PATCH] docs: clarify the security process in the triage role --- Triager-Guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Triager-Guide.md b/Triager-Guide.md index c15e6be531..65aff265f0 100644 --- a/Triager-Guide.md +++ b/Triager-Guide.md @@ -68,3 +68,5 @@ If you have questions feel free to reach out to any of the TC members. - For recurring issues, it is helpful to create functional examples to demonstrate (publish as gists or a repo) - Review and identify the maintainers. If necessary, at-mention one or more of them if you are unsure what to do - Make sure all your interactions are professional, welcoming, and respectful to the parties involved. +- When an issue refers to security concerns, responsibility is delegated to the repository captain or the security group in any public communication. + - If an issue has been open for a long time, the person in charge should be contacted internally through the private Slack chat. \ No newline at end of file