On Fri, Oct 16, 2026 at 11:34:18AM +0200, Cristian Le via devel wrote: > On 10/15/26 19:38, Kevin Fenzi wrote: > > 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. > This is quite valuable insight, thanks for sharing. From infra perspective > is there a list of changes that would be useful to work on for the long term > maintenance of bodhi to make it easier to cross-maintain?
Well, being (re)written in flask (as most of our other apps already are) would help a lot. I think splitting the client/server was good (but that was already done). We could probibly look at moving the composing backend into openshift too (it was floated a number of years back, but there were issues, many of which are probibly solved now, or at least could be revisited). ...snip... > > Tracking what? The long term idea of re-writing it? > Yes, basically. If I were, I would split it into 2 kind of tickets: > - What are the issues we should work on for the bodhi maintenance, and in > which direction. There are thoughts scattered throughout the github > fedora-infra/bodhi, so maybe just coordinating there would be enough Yeah. There's a bunch of old tickets and it's hard to find things. Probibly needs a group of folks to get together and triage/prioritize. > - Gather what bodhi actually does (and how?) so we have a clearer picture. > It does seem that there are components that it should not be handling by > itself like that emails as it was mentioned Yeah. > > 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. > Open to suggestions. Just continuing the bikeshedding in this thread? There > is a lot of context already shared here, so probably not a bad option I > guess. Yeah, and/or trying to get a group together to hash out plans more real time and come back here with a proposed plan for others to look at. 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
