Make Threat Insights BE trainee maintainers for security report schemas
Why is this change being made?
We have an OKR to add more maintainers to the security-report-schemas project.
This MR adds everyone in @gitlab-org/secure/threat-insights-backend-team as a trainee maintainer (with the exception of @ghavenga who is new to the team and has been added as a reviewer, and @subashis who was already a trainee maintainer).
For the people tagged here:
- Please tick your name after you've followed the instructions for Becoming a maintainer:
-
(already done) @subashis -
(not applicable) @ghavenga -
@jschafer -
@minac -
@Quintasan
-
- Leave a comment with a link to the trainee maintainer issue.
- Last person to tick their name, please tag me for merging this MR.
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.
Edited by Jonathan Schafer