Replace Dominic as Supply Chain Security AppSec Advisor
What?
Replace Dominic as Supply Chain Security AppSec Advisor
Why is this change being made?
Since moving to the Product Security Engineering team, Dominic Couture is no longer actively involved in the Software Supply Chain Working group at GitLab.
I think it'd be good to have some AppSec involvement and representation in this working group, as AppSec is working on a number of KRs and initiatives intended to improve and enhance Software Supply Chain Security at GitLab.
This was identified as a recommendation in FY24 AppSec OKR here: https://gitlab.com/gitlab-com/gl-security/appsec/appsec-team/-/issues/484#note_1740588366 This MR was prompted by discussion in #wg_software_supply_chain
Closes https://gitlab.com/gitlab-com/gl-security/appsec/appsec-team/-/issues/558
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
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, and the content is SAFE
-
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 by
section 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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-