Replace ~"Accepting merge requests" with %"Backlog (Accepting merge requests)"
This was brought up in https://docs.google.com/document/d/1dAs9HoAbuiRzYYvk-AFMggbN-1Hb1l6L17jMzLePbkA/edit and @meks mentioned in https://gitlab.slack.com/archives/C39HX5TRV/p1536867044000100
I think it should be fine quoting here:
Mark: Proposal: Remove
Accepting Merge Request
label. RenameBacklog
milestone toBacklog - Accepting Merge Requests
. The label is misleading in that it implies only “vetted” issues can be contributed to, but should everything be open to contribution by default? The overhead of having PMs add the label is not just a waste, it does a disservice to the community. Everything in the backlog should be open to contribution. In fact, even if something has a milestone, if the community wants to implement it sooner, then go for it! We recently had an MVP contributor that did exactly that. I’d argue that we should just drop the concept of accepting merge requests completely, but there’s still value in saying we accept them to encourage users to think about it.
One concern @markglenfletcher brought up is:
I think this works fine for bugs, but feature proposals often need direction from the
UX
team before a contributor can pick it up and run with it🤔
For the references, all issues with ~"Accepting merge requests"
are:
- ~"Accepting merge requests"
- At the moment, there are 752 open issues.
All issues with %"Backlog (Accepting merge requests)"
are:
- %"Backlog (Accepting merge requests)"
- At the moment, there are 2418 open issues.
The concerns I could think of are:
-
Issues having ~"Accepting merge requests" and %"Next 3-4 releases" or alike.
-
Issues requires ~"UX ready" while in Backlog (Accepting merge requests. i.e. What if the issues are not ready and not well defined yet? In the current documents, we define ~"Accepting merge requests" by:
- We already agreed on,
- Are well-defined,
- Are likely to get accepted by a maintainer.
I think we need to look through the current issues in Backlog (Accepting merge requests) before we make a decision.
Involving coaches @rymai @jameslopez @smcgivern @ClemMakesApps @kushalpandya @oswaldo. Involving product managers on the documents @markpundsack @akaemmerle @bikebilly @jlenny @jramsay Involving UX on the documents @sarrahvesselov
Sorry if I got the ping wrong.