I visit bugzilla often to see if I can help with package reviews and today I thought I should go and find some bugs I can help with but bugzilla seems to be quite empty.
Apparently most of the bugs are filled in their own projects in Pagure, which seems to be automatically migrated to Forge recently due to Pagure decommission.
At the moment I’m slightly confused as it seems like Bugzilla and Forge are serving very similar purpose.
Then there is Dist-Git (I hope I call it right) where all the RPM sources are.
I have three questions:
Is the plan to gradually move Bugzilla processes to Forge as well? (like package reviews for example, which seems like people wanted to do - 1,2).
How do you know where to fill a bug when you encounter one? Is it bugzilla or forge? Or both? I can imagine bugs that are fedora related but in codebases that are outside of Forge should be filled in bugzilla for tracking purposes but in theory it should be possible to have external-bugs on Forge to track these kind of stuff.
Are there any plans to move Dist-git to Forge as well?
Could you please share your mental map with me around these 3 projects and their future (the one you’re aware of). I hope I’m not the only one who is confused.
I just went through the suggested topics but they didn’t give me much clarity. In fact I just found out about https://issues.redhat.com/ which also seems to be a bugzilla replacement/counterpart.
So far it looks like people are sort of agree on Bugzilla not serving the purpose really well.
But people are not fully agree on what to do next. Am I understanding it right?
I think at this stage “clarity” for me would be understanding of these points:
is there an agreement we want to replace bugzilla with something?
is there an agreement about what to do with dist git?
is there any SIG related to any of the points above?
I think the plan is to move to use forgejo for all the issue tracking.
But until that migration happens bugzilla is where bugs against packages are filed.
I guess that issues.redhat.com is for redhat bugs not fedora bugs maybe?
I think bugzilla will not be phased out until src.fp.o is migrated.
Oh—what packages are you looking at? Bugzilla is very active—I get loads of bugs XD
No, this is not the case. There may be packages where the upstream repo is on Pagure/GitHub/Gitlab/wherever, and then we may file bugs there directly—because package maintainers do need to keep in touch with the developers (and pass patches/bugs on).
Yes—this is where the spec sources are. This is different from pagure.io (which is being sunset), but src.fedoraproject.org is not yet being sunset.
Yes there have been discussions, but I’m not aware of any concrete plans to do this yet.
Bugs for Fedora packages may be filed on the bugzilla, or at upstream projects. If they are filed on bugzilla, package maintainers triage them and then may file them upstream anyway. This is left to the reporter.
Yes, this is being discussed. Once pagure.io has been migrated completely, and the remaining bits are in place, the idea is that src.fp.o will also run on forgejo.
note: moving to a new platform is a LOT of work, which is why it takes time and needs lots of planning/buy in from the community. The move to forgejo from pagure.io is in progress, but there’s so much still to be done there. the infrastructure team handles it, so if you speak to them, they’ll be able to point you to all the work that has gone into it:
Nice! I think pointing me to the infra team is the best answer I could get. Thank you guys. I’ll poke around Making sure you're not a bot! and see if I can be useful there.
dist-git and “our” (Fedora/Redhat) bugzilla instance are about the “packaging aspect” of packages (rpm spec and what it needs)
upstream source forges and trackers (be it github, gitlab, codeberg, pagure which is moved to forge.fp.o now) are about the actual app/program/…
The first one is also the first stop for users of our packages to clarify whether a bug or request is packaging-related or something for upstream.
For the second one, “pagure.io” is decommissioned, and strictly Fedora projekt related parts have been moved to forge.fp.o. Other had to be moved elsewhere.
Ankhur mentioned the discussion about moving dist-git to a forgejo instance. I’d be surprised if the corresponding bug tracker wouldn’t move off bugzilla (to forgejo issues), but this is undecided and has to be until the feasibility is clear.
bugzilla.redhat.com and src.fedoraproject.org are for packages in Fedora Linux. ie, bugs on packages and the src/spec/build instructions to build them. This has not changed. It likely will in coming years, but there will be lots of discussion and setup and announcements around that, so I wouldn’t worry about it right now.
pagure.io is our ‘general source forge’. It was intended to house any open source projects that wanted to use it. It is being turned read-only at the end of next month (july 31st). That may change, but thats the plan now. We are urging everyone with projects there to move them elsewhere. There are some excellent choices of open forges out there, so we don’t want to stay in the business of operating a general forge.
forge.fedoraproject.org is our new code forge based on forgejo. It’s a narrower scope than pagure.io was, it’s intended for projects related to Fedora only. So, pagure.io projects that are very fedora related move here, but other projects that aren’t so tied to fedora should move to codeberg or gitlab or fossil or whatever they prefer.
Yes—everything else (including non Fedora Flatpaks) cannot be reported to bugzilla—they wont even exist there.
For rpms from non Fedora sources, dnf info may or may not include information on the URL—this depends on whoever created the rpm (since they dont have to follow the fedora packaging guidelines and can do whatever they wish with the rpm..)