Update guidance for cover image license, MVP nominations and merge settings
Why is this change being made?
This MR updates the guidance:
- Cover image license - The cover image license is only necessary if 3rd party images are used for the cover image. Starting 16.0 the marketing team provides pre-created images that do not require the licensing information to be populated. This MR guides the RPM to remove the cover image license block (
cover_img
) when using GitLab-generated images. - MVP nominations - Adds a task to remind and engage with the contributor success team on the MVP nominations for the RP and to verify that the content has been updated and rending correctly.
- Explicitly list the settings for the merging the MR:
- uncheck
Delete source branch
- check
Squash commits
- uncheck
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
-
Edited by Sampath Ranasinghe