Skip to content

Remove automated MVP nomination issue

Daniel Murphy requested to merge gitlab-community/www-gitlab-com:remove-automated-mvp-issue into master

Why is this change being made?

This MR removes the automated MVP nomination issue process from the release_post.rake. The Contributor Success team now runs a rolling nomination for the MVP selection process across the entire major milestone so there is no longer a need to generate individual milestone nomination issues each release post. See the current MVP nomination issue for 17.0 through 17.11 here: gitlab-org/developer-relations/contributor-success/team-task#490

Additionally this MR

  • Removes the old issue template under the www-gitlab-com project.
  • Replaces the old sample description in the mvp.yml with a few lines about the process or where the RPM can check in for more info.

Questions

  • The release post MR included a link to the auto generated MVP nomination issue description.gsub!('MVP_ISSUE_LINK', mvp_issue.web_url)
    • Should we include the link to the current rolling nomination issue and update this every year?
    • Is there another way of grabbing the current rolling nomination issue so the release_post.rake would not need to be manually updated?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

CHANGEME - add the details saying why, not just what.

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
  • 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

Merge request reports