It’s been two weeks since the topic started. Time for an update…
Bad news
Badges is still in bad shape. I spent some time, probably way too much, trying to improve the current state of affairs. Unfortunately, I wasn’t able to. Processing gets stuck at least once a day with the message queue overflowing and occasional crashes thrown in for good measure. This usually results in messages having to be dropped, meaning users miss out on badges they qualify for. 
There was almost no response to my mail sent out on the mailing list and to sysadmin-badges-members. I assume most of them have moved on or are busy with other things.
Good news
I made a start with getting the open issues categorized, setup a board for artwork and badge requests and added tickets to them according to current status. I hope this makes it easier for the groups involved in badges to organize tickets and manage their workflow. Feedback is welcome.
A large part of my available time for Badges in the past two weeks was spent on getting acquainted and getting access to the backend of the frontend. Yes, the frontend has its own backend! 
Plans
In the coming weeks I intend to go through open tickets, update, categorize and close as applicable. There are two main categories it seems:
- Badges not awarded
- Badge ideas/requests
I will also contact current members of fedora-badges again and clean up the group in due time to get a better picture of who’s still active and who’s not.
@erolkeskin is working on a PoC for a new/rewritten badges backend using fedora-messaging. I’m looking forward to the proposal and hope help will arrive implementing it. Looking at the current state of Badges, the urgency for replacing fedmsg-hub is quite high. It might well be the only piece of software in Fedora Apps that still relies on Python 2. 