On Thu, Oct 15, 2026 at 04:18:06PM +0200, Cristian Le via devel wrote: > Firstly I like and appreciate the role that bodhi has in our infrastructure > and this discussion is not about changing the current workflow.
...snip... > Long term future > > So what do we do for the long term? Mattia has a point about the need to > rewrite or at least refactor away from the unmaintained dependencies. But > life happens to us all and how many people do we have available to work on > that? Several other folks in infra have also expressed desire to re-write it. It's somewhat of an outlyer in terms of frameworks (it's the only thing using pyramid), it's the only thing handling it's own email sending, it's setup very differently than our other flask apps. > In tangentially relevant insight from Redhat, they are also trying to find a > solution for a system for more general aggregation of test results, and they > are open to expanding the scope to manage gating, so it may not be too far > off to consider how bodhi could fit into this. The team being formed to work > on this expressed interest in accommodating the Fedora workflow needs, and > the planning is still in early stages that this can be adapted to best fit a > bodhi replacement or individual components. I agree with Adam here. I don't think we want to add into a 'oh, and fedora too' application here. > There could well be other services that are already developed and maintained > that we could adapt to fit in or around bodhi. Do name those out if anyone > know or ping someone who might know. Yes, let's address the konflux shaped > elephant waiting for this email to be sent. > > In the same spirit as the bugzilla replacement ticket [3], I think we should > start with gathering everyone's user stories on what exactly is bodhi's role > in the current workflow in the broader picture. What do you see as the good > features of the current workflow, and what major things you find missing or > would need attention? In looking or designing an alternative, what are some > key designs that should be considered (e.g. should it be a standalone > service, or part of a bigger service)? We also need to gather the technical > side how everything connects around bodhi. > > > First step > > Before anything, where should the tracker for this thing be. As a releng or > fesco ticket? Hopefully not as an email/discussion thread? Tracking what? The long term idea of re-writing it? I personally dislike tickets for discussing plans. They lack lots of things actual discussion forums have and tend to just sit around or driving into the weeds in details. I don't know that it would make sense in either fesco or releng... if you must have a ticket, how about a bodhi one? (which I think there already is right?). kevin -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
