Skip to content

Add community contribution labels to release group page

Vladimir Shushlin requested to merge vshushlin-vshushlin-master-patch-21791-patch-33658 into master

Why is this change being made?

Following the idea from our retrospective:

We should really start using Seeking community contribution label more. Right now there are only 4 issues from our group.

A lot of times we'll see a small improvement which we know how to do but don't have the capacity for. I think every time we should just create a Seeking community contribution issue for such things.

It has a few advantages:

  1. if you forget to add an implementation guide, the bot will ping you and suggest that
  2. we use accepting merge requests for almost all the issues, and Seeking community contribution can attract much more focused attention.
  3. since these issues will have an implementation guide, and probably will be quite simple, it will be much easier to review.

See how many issues pipeline authoring has: https://gitlab.com/gitlab-org/gitlab/-/issues?sort=created_date&state=opened&label_name[]=group::pipeline+execution&label_name[]=Seeking+community+contributions

Author Checklist

  • Provided a concise title for the 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 change to the correct DRI(s)
    • 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 in 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 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 Vladimir Shushlin

Merge request reports