Should we move to `/contribute` link for all projects

Discuss the benefits and drawbacks for using repo-link/contribute provided by GitHub instead of issue filters we have.

This is the issue that suggested this change

This is the pull request that made the require changes.

This is a comment in the pull request suggesting that this might not be at the best interest of users.

@sara-02 , @gavv , @tiferet, shall we discuss and figure this out?

[tiferet]

Not yet. We’re shipping a major new version soon and will write about it then.

Right now it’s a very simple algorithm. Basically it just surfaces all issues that have any of about 300 labels we’ve identified as be synonyms for either good first issue or documentation. It ranks them both by the relevance of their labels and by their recency.

The next version will try to surface additional issues that haven’t been manually labeled, but will still uprank all the issues that do have these labels.

I think the problem @gavv had was specific to that project, where they use the the help wanted label instead of good first issue or one of its synonyms. We’ve purposely kept help wanted out of the list, because the feedback we got from maintainers was that it often indicates a harder issue, that needs more extensive work, and not at all a beginner-friendly issue.

One option would be to just revert to a manual filter specifically for the Roc repo, and keep the /contribute link for most repos, which do use the labels on our list.

Incidentally, if anyone has labels they use that they would like to see added to the list, we can look into doing that, but the help wanted label in particular seems to be problematic for many repos…

[sara-02]

Even I need to read how the /contribute attribute works, lets sync on this once we have an idea about its working, then we can see if it works for a majority of the cases or not.