Improve "Issue"-labels

Feature Request

Is your feature request related to a problem? Please describe.

A lot of newcomers have trouble finding easy issues to contribute to. We should add labels which easy the process of choosing issues.

Describe the solution you’d like

I would recommend judging the issues in different dimesnions:

• Complexity
• Effort (e.g. effort2: days-label)
• “good first issue” for easy first-time contributions
• “state: has PR”-label
• Re-evaluate “PRs Open”. It is quite confusing for a lot of contributors what this label actually means. In my opinion, it should be removed or renamed.

[boenrobot]

I think every PR is open for the community, so I do not think we need this label at all.

Well, sure, but there are some features which would be outright rejected for one reason or another, and one may not realize that until they’ve already made the feature without reading the whole discussion, so IMHO, having a label that says “this has been discussed and we would like to have it indeed, but can’t spare the time to make it, so if you’d like to contribute, go ahead, we’ll accept it” is nice.

That said, I agree the name “PRs Open” sounds very misleading.

“PRs Open” means that we’re looking for contributions (the feature/functionality/enhancement is ready to tackle). What would you propose instead?

I think a name like “PRs Welcomed” would explain the purpose better.

I’ve been reading some issues with the label “PRs Open” and thought that means “There is one or more opened PR for this issue, waiting to be reviewed later”, but only now I realize that’s not what the name “PRs Open” means.

With labels like complexity/effort, I also agree having even a rough time estimate isn’t really a good idea, as developers (in general) are notorious for underestimating the time required. I think more generic values like “trivial”, “low”, “medium” and “high” might be better.

[marcus-sa]

The severity or priority labels would be a great addition.