# 'Call for participation'-issues aggregator

**URL:** <https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492>\
**Category:** Learn\
**Created:** [January 8, 2024, 12:24pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492 "2024-01-08T12:24:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![unorsk](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/unorsk/32/3144_2.png) [@unorsk](https://discourse.haskell.org/u/unorsk)\
**Post date:** [January 8, 2024, 12:24pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/1 "2024-01-08T12:24:51Z")

</div>

I sometimes read the ‘Call for participation’ section in the Haskell Weekly newsletter. And a couple times I picked up an issue.

So I am wondering if there is a nice way to set up an aggregated list of github issues (from a number of haskell projects) tagged as ‘good-first-issue’, ‘help-wanted’ or smth like that.

Does this already exist maybe?

---

<div class="post-metadata">

**Author:** ![taylorfausak](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/taylorfausak/32/54_2.png) [@taylorfausak](https://discourse.haskell.org/u/taylorfausak)\
**Post date:** [January 8, 2024, 4:24pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/2 "2024-01-08T16:24:54Z")

</div>

You can search for issues like this using GitHub’s search. For example, to find issues in Haskell repositories that have the `help-wanted` label, you can search for `language:haskell label:help-wanted`.

[https://github.com/search?q=language%3Ahaskell+label%3Ahelp-wanted&type=issues](https://github.com/search?q=language%3Ahaskell+label%3Ahelp-wanted&type=issues)

---

<div class="post-metadata">

**Author:** ![jaror](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/jaror/32/3271_2.png) [@jaror](https://discourse.haskell.org/u/jaror)\
**Post date:** [January 8, 2024, 4:56pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/3 "2024-01-08T16:56:13Z")

</div>

You probably want to add `is:open` too: [https://github.com/search?q=language%3Ahaskell+label%3Ahelp-wanted+is%3Aopen&type=issues](https://github.com/search?q=language%3Ahaskell+label%3Ahelp-wanted+is%3Aopen&type=issues)

Or maybe `good first issue` instead of `help-wanted`: [https://github.com/search?q=language%3Ahaskell+label%3A"good+first+issue"+is%3Aopen&type=issues](https://github.com/search?q=language%3Ahaskell+label%3A%22good+first+issue%22+is%3Aopen&type=issues)

Actually `"help wanted"` with a space instead of a dash gives much more results: [https://github.com/search?q=language%3Ahaskell+label%3A"help+wanted"+is%3Aopen&type=issues](https://github.com/search?q=language%3Ahaskell+label%3A%22help+wanted%22+is%3Aopen&type=issues)

---

<div class="post-metadata">

**Author:** ![simonmic](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/simonmic/32/1796_2.png) [@simonmic](https://discourse.haskell.org/u/simonmic)\
**Post date:** [January 9, 2024, 3:46am UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/4 "2024-01-09T03:46:41Z")

</div>

That’s tempting, and I used to tag issues like that. But for whatever reason it seemed not to work -

- they were roundly ignored
- help-wanted implies help-not-wanted on the others; but help is wanted everywhere
- good-first-issue or easy-issue are highly relative and when I reviewed them later they all seemed way too much to ask of someone browsing for actually easy first issues. Maybe my project didn’t have any ?
- people able to help on issues will find them, so this seemed wasted work

---

<div class="post-metadata">

**Author:** ![unorsk](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/unorsk/32/3144_2.png) [@unorsk](https://discourse.haskell.org/u/unorsk)\
**Post date:** [January 10, 2024, 3:46pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/5 "2024-01-10T15:46:54Z")

</div>

Yeah, this one’s nice!

The problem is that different people/repos use different labels which makes it a bit harder.

But I was more thinking of a way to both stimulate people creating new ‘help-wanted’ issues and make it easier to those who want to contribute finding those issues.

---

<div class="post-metadata">

**Author:** ![unorsk](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/unorsk/32/3144_2.png) [@unorsk](https://discourse.haskell.org/u/unorsk)\
**Post date:** [January 10, 2024, 3:58pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/6 "2024-01-10T15:58:57Z")

</div>

It would be nice to find out what is actually preventing people from contributing. I guess the size of the community is a big factor here 🙂 but may be some other reasons?

I’d guess some people might have questions re issues in question but would just be too shy ask openly for whatever reasons. One of the reasons could be that often it’s not clear who should you ask.

A couple times I myself was in a situation where I make a PR but don’t know who exactly should I talk to about it (when no one got assigned automatically)

And then I like what @taylorfausak does with the newsletter – once I see an issue I’m like, oh, that sounds interesting. But otherwise I wouldn’t even bother going on github and filtering issues by label. Similar to how ads work.

---

<div class="post-metadata">

**Author:** ![michaelpj](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/michaelpj/32/417_2.png) [@michaelpj](https://discourse.haskell.org/u/michaelpj)\
**Post date:** [January 10, 2024, 4:00pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/7 "2024-01-10T16:00:17Z")

</div>

> - help-wanted implies help-not-wanted on the others; but help is wanted everywhere

For HLS we decided to tag issues as “easy” partly as it felt a bit more objective. Of course, as you point out, it’s really not objective, but nonetheless it seems true that some issues are often easi\_er\_ than the bulk of the issues, and it makes sense to label them. We have used that labelling a bit - we use it to identify good issues for ZuriHac, for example. But I don’t know how useful it is overall.

---

<div class="post-metadata">

**Author:** ![f-a](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/f-a/32/2740_2.png) [@f-a](https://discourse.haskell.org/u/f-a)\
**Post date:** [January 12, 2024, 5:08pm UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/8 "2024-01-12T17:08:48Z")

</div>

An example of [such an aggregator](https://climatetriage.com/) (not Haskell related) launched recently.

---

<div class="post-metadata">

**Author:** ![tomjaguarpaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/tomjaguarpaw/32/1230_2.png) [@tomjaguarpaw](https://discourse.haskell.org/u/tomjaguarpaw)\
**Post date:** [January 17, 2024, 10:12am UTC](https://discourse.haskell.org/t/call-for-participation-issues-aggregator/8492/9 "2024-01-17T10:12:01Z")

</div>

> [@unorsk](#):
>
> So I am wondering if there is a nice way to set up an aggregated list of github issues (from a number of haskell projects) tagged as ‘good-first-issue’, ‘help-wanted’ or smth like that.

I think this is a good idea. If I was implementing it I would start very simply, by creating a GitHub repo and using the issue tracker to manually link to “good first issues” on other projects. If it proves useful then there are various ways of automating it, but I wouldn’t put the effort into automation until its value has been demonstrated.