Pick good first issues as a priority

[LouiseBonnard]

👋 @schneems, thank you very much for this promising project!

I'll speak for PrestaShop, as one of its Product Manager, but I guess it might be interesting for every open source project using it.

Indeed, the team has recently decided to use new leverage to help new contributors participate in the PrestaShop open source project on GitHub: the good first issue label which designates supposedly simple bugs or improvements that do not have any pull request linked yet. See list.

Currently, it looks like all issues CodeTriage send to subscribers are randomly picked. Read https://github.com/codetriage/CodeTriage/issues/847#issuecomment-460738673. Following what you said in this issue, I wanted to suggest the distribution system to start with labels especially made for beginners, like the good first issue label in PrestaShop, before moving to standard issues.

What do you think? Would it be possible to add this parameter to the random selection of issues?

🙂

[wagnerluis1982]

Hi, codetriage user for some months, first time in the codetriage issues :smile:

I like this idea of prioritize good first issues. I add only to not use fixed label:"good first issue" label as reference (although can be a default). What I mean is to allow in codetriage's project configuration to set what label is used for this purpose, perhaps extending to describe more than one label (e.g. to also prioritize "help wanted" label).

Listing some patterns I found in popular projects:

• label:"status: ideal-for-contribution" : spring-boot
• label:"hotlist: community-help" : angular
• label:"contribution welcome" : vue.js
• label:"Good First Issue" : readthedocs.og

[LouiseBonnard]

FYI @marionf