Contributors (dropdown) → New Contributors → Easy Fix
Click on various listings. Many will be: closed, out-of-date, marked completed, or open (but already completed) (Ref: 183, 189, 199, 207, 528, 534, 732, 2413, etc.)
Impact
Bad first impression for new contributors.
New Contributors will have to sift through many entries to find relevant ones
Possible long-term fix
Some kind of RSS feed of GitHub/pagure issues that open, and labeled noob-friendly.
Most of the links in the top bar being 404s doesn’t help, either.
It’s starting to look like that site would be better served by someone taking it out back and putting it out of its misery, than bothering to “fix” it.
But I agree it’s definitely reflecting poorly on the project, while it’s still looming there like the creeping undead.
I had proposed retirement (when I was in the room with the Fedora Council at Frankfurt F2F 2023) of the service (and that for WCIDFF as well) a couple of years back and I would propose the same here too. There has been enough time spent on understanding how we can get the value out of it and every single time, we have realized that it is less of a platform problem and more of a people problem.
I’m +1 for retirement as well, it is a nice page, but it’s no longer helpful at all. It would rather be better to have some kind of crossroads that will point people to correct places where to look. They can always look for anything with EasyFix, FirstIssue and so on in the tracker of the project they care about.
For the purposes on my livestreams, I’ve cobbled together this easyfix page from the remnents of the previous codebases, it’s not great but it’s somewhat up-to-date. It still uses the wiki as a database for projects to crawl, though, so, not ideal at all.
I had submitted a proposal for an outreachy intern to redo this page properly, but it didn’t make the cut.
If anybody wants to work on a nice easyfix page, I think it would be very useful work, and I’m happy to help.
Perhaps we could discuss how to make it more useful then?
The problems I have with it:
easyfix is very subjective. It might be something I think is easy, but
turns out it’s not to others, or they need additional privs or…
In any kind of active project it’s hard to keep them around…
If I see something in infra that I think would be really easy for
someone new to do, I can mark it, but usually someone actually wants
that thing to be done, so I can’t just ignore it. Or something comes
along that I can do in like 1 minute, it’s hard to want to file a issue,
wait for someone for some time and then remmeber to go back to it.
There’s some places that have something similar to this, but different:
“good first issue” https://goodfirstissue.dev
Or we could try and better codify what a easy fix is and how long we
wait for it to be taken by someone?
As a side note, the current easyfix this thread was started about is a
python (2!) script running on sundries servers that is of course broken
because there’s no python2 there and its redirecting all it’s output to
/dev/null so no one noticed. It might be that could easily be fixed
if we want to update the site again until we figure out what to do with
it.
Oh no I don’t want to keep that easyfix
But I’d like to keep the EasyFix wiki page around, if it’s not too much of a pain.
You can totally kill the page generated on sundries.
