Add guidance for new joiners to reach out to staff appsec engineers
Why is this change being made?
This MR is adding a suggestion for new joiners to reach out to Staff appsec engineer(s) if needed, rather that the whole team.
We are trying this as we will see how it goes when we do retire Staff appsec engineer(s) from all rotations.
The objective of doing it this way is that the Staff still keeps in touch with rotations, even if he doesn't do it anymore.
Related issue: https://gitlab.com/gitlab-com/gl-security/appsec/appsec-team/-/issues/343
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained bysection on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.