There are several long awaited requests on Bodhi: - split bodhi-server, bodhi-client, bodhi-messages - provide a RESTFUL interface - switch both server and client to use OpenID Connect - split the monolithic models.py module into smaller, more manageable modules
Since any of these would require a big code refactoring, I wonder how hard it could be to also move the server from using Pyramid to Flask. Bodhi is the only CPE project using Pyramid, as far as I know, and it seems to me that Flask would be easy to maintain and to get community contributions.
As we're approaching a new year, I would simply ask if there's room to deploy some hours from the budget to make this change. And if it could be worthwhile.
This will be worthy of initiative https://docs.fedoraproject.org/en-US/cpe/initiatives/ Could you propose it as one?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: dev, high-gain, high-trouble
so, first my standard disclaimer: I think discussion is better on list or irc/matrix, etc. Tickets are great for 'Do X' but lousy for 'Discuss what we want to do'. :)
That said, I don't particularly have any strong feelings for this. Re-writing things is dangerous ( see https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ if you haven't already) but having this using the same framework would have some advantages. Bodhi is the most complex app we maintain I think...
As suggested from @zlopez I've opened https://pagure.io/cpe/initiatives-proposal/issue/16 so I think the discussion can continue there.
I agree that re-writing things is a risk, but I think trying to maintain code based on a totally different platform from what we're using in other app is a big waste of time. Bodhi has now almost 300 tickets open, the oldest is from 2014, but the pile is constantly growing... I hope that with a common ground with other apps we can address issues in a quicker way.
ok. Lets close this in favor of the upstream one then. Thanks!
Metadata Update from @kevin: - Issue close_status updated to: Initiative Worthy - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.