Clarify "Accepting Merge Requests", "up-for-grabs" and "first-timers-only" labels
Accepting Merge Requests:
Features that we may not have scheduled for a specific release yet, but would gladly receive merge requests for
up-for-grabs:
Issues that can be picked up by anyone who wants to contribute to GitLab but is not sure where to start. Merge request coach: @rymai
first-timers-only:
Issues suitable for first time contributions to Open Source Software. See: http://www.firsttimersonly.com/ Contact: @markglenfletcher
My understanding of the differences between them is is:
- Accepting Merge Requests - requirements are defined, it's not super critical for GitLab team, but anyone is welcome to contribute
- up-for-grabs - requirements the same as for "Accepting Merge Requests" plus it doesn't require a huge knowledge of GitLab codebase; it will probably involve only small, local changes; no big refactorings required upfront
- first-timers-only - requirements the same as for "up-for-grabs" but it's super easy so we reserve it for people with no prior open source experience
I think that we should discuss it, include it in Handbook and maybe improve labels' descriptions.