Merge branch 'jh-improve-contribution-guidelines' into 'master'

Update Contribution Guidelines for Wider Community

See merge request https://gitlab.com/gitlab-org/gitlab-pages/-/merge_requests/892

Merged-by: Jaime Martinez <jmartinez@gitlab.com>
Approved-by: Jaime Martinez <jmartinez@gitlab.com>
Reviewed-by: Naman Jagdish Gala <ngala@gitlab.com>
Co-authored-by: Naman Jagdish Gala <ngala@gitlab.com>
Co-authored-by: John Hope <jhope@gitlab.com>

1 files changed, 15 insertions, 16 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5742ce06..641c3eab 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -31,7 +31,7 @@ _This notice should stay as the first item in the CONTRIBUTING.md file._
   - [Subject labels (~wiki, ~"container registry", ~ldap, ~api, etc.)](#subject-labels-wiki-container-registry-ldap-api-etc)
   - [Team labels (~CI, ~Discussion, ~Edge, ~Platform, etc.)](#team-labels-ci-discussion-edge-platform-etc)
   - [Priority labels (~Deliverable and ~Stretch)](#priority-labels-deliverable-and-stretch)
-  - [Label for community contributors (~"Accepting Merge Requests")](#label-for-community-contributors-accepting-merge-requests)
+  - [Label for community contributors (~"Seeking community contributions")](#label-for-community-contributors-seeking-community-contributions)
 - [Implement design & UI elements](#implement-design--ui-elements)
 - [Issue tracker](#issue-tracker)
   - [Issue triaging](#issue-triaging)
@@ -107,7 +107,7 @@ the remaining issues on the GitHub issue tracker.
 ## I want to contribute!
 
 If you want to contribute to GitLab, but are not sure where to start,
-look for [issues with the label `Accepting Merge Requests` and weight < 5][accepting-mrs-weight].
+look for [issues with the label `Seeking community contributions` and weight < 5][seeking-contributions-weight].
 These issues will be of reasonable size and challenge, for anyone to start
 contributing to GitLab.
 
@@ -192,14 +192,14 @@ release. There are two levels of priority labels:
   milestone. If these issues are not done in the current release, they will
   strongly be considered for the next release.
 
-### Label for community contributors (~"Accepting Merge Requests")
+### Label for community contributors (~"Seeking community contributions")
 
 Issues that are beneficial to our users, 'nice to haves', that we currently do
 not have the capacity for or want to give the priority to, are labeled as
-~"Accepting Merge Requests", so the community can make a contribution.
+~"Seeking community contributions", so the community can make a contribution.
 
 Community contributors can submit merge requests for any issue they want, but
-the ~"Accepting Merge Requests" label has a special meaning. It points to
+the ~"Seeking community contributions" label has a special meaning. It points to
 changes that:
 
 1. We already agreed on,
@@ -207,11 +207,11 @@ changes that:
 1. Are likely to get accepted by a maintainer.
 
 We want to avoid a situation when a contributor picks an
-~"Accepting Merge Requests" issue and then their merge request gets closed,
+~"Seeking community contributions" issue and then their merge request gets closed,
 because we realize that it does not fit our vision, or we want to solve it in a
 different way.
 
-We add the ~"Accepting Merge Requests" label to:
+We add the ~"Seeking community contributions" label to:
 
 - Low priority ~bug issues (i.e. we do not add it to the bugs that we want to
 solve in the ~"Next Patch Release")
@@ -219,18 +219,17 @@ solve in the ~"Next Patch Release")
 the ~UX / ~"Product work" is already done
 - Small ~"technical debt" issues
 
-After adding the ~"Accepting Merge Requests" label, we try to estimate the
+After adding the ~"Seeking community contributions" label, we try to estimate the
 [weight](#issue-weight) of the issue. We use issue weight to let contributors
 know how difficult the issue is. Additionally:
 
-- We advertise [~"Accepting Merge Requests" issues with weight < 5][up-for-grabs]
+- We advertise [~"Seeking community contributions" issues with weight < 5][seeking-contributions-weight]
   as suitable for people that have never contributed to GitLab before on the
   [Up For Grabs campaign](http://up-for-grabs.net)
 - We encourage people that have never contributed to any open source project to
-  look for [~"Accepting Merge Requests" issues with a weight of 1][firt-timers]
+  look for [~"Seeking community contributions" issues with a weight of 1][first-timers]
 
-[up-for-grabs]: https://gitlab.com/gitlab-org/gitlab-pages/issues?label_name=Accepting+Merge+Requests&scope=all&sort=weight_asc&state=opened
-[firt-timers]: https://gitlab.com/gitlab-org/gitlab-pages/issues?label_name%5B%5D=Accepting+Merge+Requests&scope=all&sort=upvotes_desc&state=opened&weight=1
+[first-timers]: https://gitlab.com/gitlab-org/gitlab-pages/-/issues/?sort=popularity&state=opened&weight=1&label_name%5B%5D=Seeking%20community%20contributions
 
 ## Implement design & UI elements
 
@@ -382,7 +381,7 @@ A recent example of this was the issue for
 We welcome merge requests with fixes and improvements to GitLab code, tests,
 and/or documentation. The issues that are specifically suitable for
 community contributions are listed with the label
-[`Accepting Merge Requests` on our issue tracker for Pages][accepting-mrs],
+[`Seeking community contributions` on our issue tracker for Pages][seeking-community-contributions],
 but you are free to contribute to any other issue you want.
 
 Please note that if an issue is marked for the current milestone either before
@@ -391,7 +390,7 @@ in order to ensure the work is finished before the release date.
 
 If you want to add a new feature that is not labeled it is best to first create
 a feedback issue (if there isn't one already) and leave a comment asking for it
-to be marked as `Accepting Merge Requests`. Please include screenshots or
+to be marked as `Seeking community contributions`. Please include screenshots or
 wireframes if the feature will also change the UI.
 
 Merge requests should be opened at [GitLab.com][pages-mr-tracker].
@@ -585,12 +584,12 @@ available at [http://contributor-covenant.org/version/1/1/0/](http://contributor
 [team]: https://about.gitlab.com/team/
 [getting-help]: https://about.gitlab.com/getting-help/
 [codetriage]: http://www.codetriage.com/gitlabhq/gitlabhq
-[accepting-mrs-weight]: https://gitlab.com/gitlab-org/gitlab-pages/issues?assignee_id=0&label_name[]=Accepting%20Merge%20Requests&sort=weight_asc
+[seeking-contributions-weight]: https://gitlab.com/gitlab-org/gitlab-pages/-/issues/?sort=weight&state=opened&label_name%5B%5D=Seeking%20community%20contributions&assignee_id=None
 [pages-tracker]: https://gitlab.com/gitlab-org/gitlab-pages/issues
 [google-group]: https://groups.google.com/forum/#!forum/gitlabhq
 [stackoverflow]: https://stackoverflow.com/questions/tagged/gitlab
 [fpl]: https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=feature+proposal
-[accepting-mrs]: https://gitlab.com/gitlab-org/gitlab-pages/issues?label_name=Accepting+Merge+Requests
+[seeking-community-contributions]: https://gitlab.com/gitlab-org/gitlab-pages/-/issues/?label_name%5B%5D=Seeking%20community%20contributions
 [pages-mr-tracker]: https://gitlab.com/gitlab-org/gitlab-pages/merge_requests
 [gdk]: https://gitlab.com/gitlab-org/gitlab-development-kit
 [git-squash]: https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits