From 6c32387febede8105787e80bf21c805afefb54f3 Mon Sep 17 00:00:00 2001 From: przsus <101723670+przsus@users.noreply.github.com> Date: Thu, 5 Dec 2024 09:18:59 +0100 Subject: [PATCH] update contact info --- docs/CODE_OF_CONDUCT.md | 3 ++- docs/SECURITY.md | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md index 8aae7c1..52749bc 100644 --- a/docs/CODE_OF_CONDUCT.md +++ b/docs/CODE_OF_CONDUCT.md @@ -56,7 +56,8 @@ a project may be further defined and clarified by project maintainers. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team at [oss-conduct@cisco.com][conduct-email]. All +reported by contacting the project team at [ssalemar@cisco.com][Shivram Salem Arunachalam], +[acichon@cisco.com][Arkadiusz Cichon] or [sprzemys@cisco.com][Przemyslaw Susko]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. diff --git a/docs/SECURITY.md b/docs/SECURITY.md index 5031a48..292489e 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -14,7 +14,7 @@ This document outlines security procedures and general policies for the [ansible The [ansible-collection-sdwan](https://github.com/cisco-open/ansible-collection-sdwan) team and community take all security bugs in [ansible-collection-sdwan](https://github.com/cisco-open/ansible-collection-sdwan) seriously. Thank you for improving the security of [ansible-collection-sdwan](https://github.com/cisco-open/ansible-collection-sdwan). We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions. -Report security bugs by emailing oss-security@cisco.com. +Report security bugs by emailing [ssalemar@cisco.com][Shivram Salem Arunachalam], [acichon@cisco.com][Arkadiusz Cichon] or [sprzemys@cisco.com][Przemyslaw Susko]. The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.