1. You are here:
2. Handbook
3. Marketing
4. Community Relations
5. Contributor Success Team
6. GitLab MVP Selection Process

Maintained by:

On this page

• On this page
• GitLab MVP Selection Process
  • GitLab MVP
  • Workflow for selecting GitLab MVP
    • MVP Eligibility
    • MVP Write-Up Blurb
  • Sending MVP Appreciation Gifts
  • Suggested language for MVP Swag email, or Twitter DM:

GitLab MVP Selection Process

GitLab MVP

Each release post GitLab recognizes a community contributor as the MVP ("Most Valuable Person") for the release. Beginning with the 15.9 release, the Contributor Success team took over the nomination and selection process for the GitLab MVP. These community contributors are recognized within the GitLab release post and across Slack and Discord. MVPs also receive a GitLab swag pack in celebration of their contribution.

• Hall of fame list of GitLab MVPs
• Release posts on GitLab blog

Workflow for selecting GitLab MVP

1. A nomination issue is automatically generated on 3rd of the month.
2. Link to the nomination issue on Slack channels in #release-post, #community-relations, #mr-coaching and #core after issue is created.
3. Encourage team members to vote by sharing reminders in the above Slack channels.
   • Complete by 12th of the month or earliest business day.
4. Select the MVP in the nomination issue by choosing the eligible nominee with the most votes
   • Votes are cast as :thumbsup: emojis under the nominee thread in the issue. Other emojis are not counted, but if a vote is close please remind voters they must use the :thumbsup: to vote.
   • Complete by 15th of the month or earliest business day.
   • If no MVP nominations have been added to the MVP issue by the 15th or earliest business day, resend reminders to the Slack channels by sharing the original solicitation posts again. Ping the channel and note the lack of nominations and due date. E.g. in #community-relations:

        @community-team - We only have one (or none) MVP nomination. I’m going to wait until the end of the day, 12pm UTC for other nominations. Please nominate a community contributor that delivered something great for X-Y!
     

5. Use the MVP write-up issue template to collaborate with the MVP winner and their nominator to create a write-up blurb for the release post.
   • Complete write-up blurb by 20th of the month
6. Announce the MVP winner in team member Slack channels and community Discord.
7. Add MVP winner to "hall of fame" data/mvps.yml file
   • Add release version, MVP name, user handle, release post date and release post URL
   • Submit by 20th of the month
8. Update the data/release_posts/x_y/mvp.yml file with MVP information. E.g.data/release_posts/15_8/mvp.yml targeting the release-15-8 branch.
   • Add MVP name, user handle and write-up blurb
   • Submit by 20th of the month
9. Mention the @community-team in the #community-relations channel and ask them to send the swag pack to the MVP.
   • Follow up with Community Relations to confirm the MVP has been sent their swag
10. Share a thanks message to team members who participated in the nomination process.
    • Link to the release post MVP section.
    • Ping any team members who added nominations, supportive comments or :thumbsup: votes within the MVP nomination issue.

MVP Eligibility

• The Contributor Success team will make the final choice on the GitLab MVP within the nomination issue and should not wait for consensus.
• While there is usually one MVP per release post, we would consider more.
• A contributor is eligible to be MVP once per major release cycle. For example, if they are MVP during any 13.* milestone, they cannot be an MVP again until the 14.0 milestone.
• A quick way to check past MVPs is to view /data/mvps.yaml..
• Contributors may be nominated whether they have contributed to the current release cycle or not. Contributors are recognized for previous and ongoing contributions to GitLab.
  • E.g. See the 15.8 MVP selected for prior release work and the 15.7 MVP selected for steady contributions.

MVP Write-Up Blurb

Use the MVP write-up issue template to collaborate on the release post blurb.

The MVP write-up section should:

• Contain a brief description of the MVP's release contribution and summary of prior GitLab contributions.
• A link to the MVP's GitLab profile.
• Any links to relevant issues, MRs, issue boards or epics the MVP contributed to.
• Contributor Success is responsible for reviewing the entry for:
  • Consistency and accuracy
  • Correct and workings links for user information, issues, MRs, etc.
  • Correct spelling of names, organizations, product features, etc.
  • Correct prounoun usage
• The write-up should be submitted by the 20th of the month to the data/release_posts/x_y/mvp.yml file targeting the specific release branch

Sending MVP Appreciation Gifts

Every release GitLab chooses a Most Valuable Person (MVP) and the Community Relations team recognizes them for their contributions.

1. Determine MVP after merge window closes, see #release-post channel
2. Find MVP's contact information
   • Contacting contributors
3. Send Swag according to our SWAG operations guide
4. Alert the release day manager that the giveaway has been sent

Suggested language for MVP Swag email, or Twitter DM:

Congratulations on being the MVP for GitLab's (enter release number here. ex. 13.3) release! 🤸‍♂️

https://about.gitlab.com/community/mvp/

We are so amazed by your work and we want to thank you for your contributions: please enjoy some well deserved GitLab swag! We can't wait to see what you do next!

Link to collect swag:

(paste swag link here, and opt to add the coupon code as well)