it’s a long known issue, they are reported
it’s knowing which tracker that’s been the hard part for me
I’ve been trying to do some “outreach” for Silverblue over the last week or two, and I’ve seen this quote - in one way or another - in a couple of places now. As it’s also a pain point for me, I thought I’d raise it - and yes, this is moaning, somewhat, but I think it’s productive to say it out loud.
It is very hard, especially for people not very engaged in the Fedora Project, to understand where anything is “done”. Off the top of my head there are three places you might file bugs against a Fedora Project (GitHub, GitLab, and Bugzilla), two additional platforms you might find code repositories (src.fpo and pagure.io), and two more platforms you might find (possibly out-of-date) documentation (wiki and docs). Builds could also be happening on GitHub, but could be happening on Koji - and I’m sure there’s a bunch I’ve missed (oh… mailing lists!).
It’s pretty common for people to file things in the “wrong place”, leading to poor interactions (especially with Silverblue, where it’s not clear if something is a Silverblue-specific bug or not). Because we’re all on different platforms it’s not possible to “move” an issue between projects, either.
I’m aware that the project takes a very hands-off approach to where things are hosted - in practice, this makes it really hard to engage with the Fedora Project as a new person and I think it’s creating some siloing as well - particularly between the “older” projects (on the self-hosted platforms) and “newer” projects (e.g. CoreOS and some of Silverblue, on GitHub).
I hope this comes across as a reflection on how, as a relative outsider, I’ve found working with Fedora - and I don’t think I’m alone (in fact, I’m sure I’m not alone). I hope this doesn’t come across as criticising anyone personally, or the intent of decisions made as a project - I understand the desire to keep people and teams using the tools they’re happy with, and of course any project that’s been going on for decades is going to have some “baggage” to deal with.
As the person complaining, I would like to propose an action (in an effort to make this productive, rather than because I necessarily think it’s the best one). Maybe it’s worth putting together a “Rationalisation Working Group” that focuses on documenting the landscape, seeking consensus on platform usage, and then doing the engineering work to meet that consensus. (Maybe this already exists? If so, where could I read about it?)
Other people probably have better ideas!