I’m glad to announce that after much discussion the first steps have been taken to get Fedora Badges back in shape again.
Based on all the feedback received so far, Fedora Badges is still much liked throughout the community. Therefore, getting it back in shape should be a reward in itself.
Next Steps
There are many ideas floating around on how to go forward with Fedora Badges (see discussion). None have materialized further than discussion in various channels. I would therefore like to seize the opportunity and outline the next steps and where we think the ideas brought forward would fit in.
Short Term
The short term goal is to get on top of the current state of affairs. Along the way roadblocks will undoubtedly be encountered. So, items may move as appropriate.
- Sort out tickets in Pagure (currently 145 open issues)
- Close outdated tickets
- Tag tickets according to badges component or personas (as suggested in Fedora Badges - User Stories brainstorm meeting - Fedora Discussion by @cverna, @jflory7 et al.)
- Process issues, badge requests
- Update documentation (outdated references, etc.)
- Attempt to get the backend in a reliable working state
- Document issues and possible solutions
- Apply hotfixes as needed
I’m, personally, in favour of using Pagure as the issue and task tracker and distribute work from there by way of GitHub issues in the appropriate component (tahrir, tahrir-api, fedbadges, datanommer).
Automate this, so that assigning a label in Pagure will automagically create an issue on GitHub for the correspondig project.
Medium Term
This is were fundamental decisions need to be made regarding frontend, backend refactoring or rewrite and such. Depending on the amount of work involved there may be intermediate solutions to persue and larger projects moved to the long term.
- Decide on the frontend
- Tahrir is written in Python2, so needs an overhaul, if we decide to keep it
- Use Discourse as the frontend tied to this forum as suggested and followed up by @mattdm
- Use badgr-server as a replacement for tahrir (upstream project no longer exists, though)
- Shape up the backend
- Move from fedmsg to Fedora Messaging
- Move from datanommer to datagrepper
- Move from openid to oidc for authentication
There’s a helpful document in the fedora-infra repo.
Long Term
What goes here pretty much depends on what we encounter and come up with in the long and medium term. So, we leave it open for now.
Contributing
As I have experienced myself, it currently takes quite some effort to onboard the fedora-badges. I sincerely hope that will change once documentation has been updated and word about the current effort is spreading.
Nonetheless, help is welcome in all areas mentioned above and maybe others as well. Once the fedora-badges project in Pagure has been brought into shape, issues and tasks will appear there and everyone is welcome to contribute.
Since Fedora Badges is made up out of different components, some of which have already been deemed to be replaced/refactored. Work in different areas will happen in parallel (e.g. short term fixing of the environment and mid/long term refactoring of fedbadges).
I will be focusing on the short term items in the coming weeks, while @erolkeskin has already started work on the backend.
Communication
Updates regarding progress will be posted regularly in this thread. Make sure to watch this topic and any updates will be delivered to your inbox.
Or, if you really want to stay on top of everything regarding Fedora Badges, watch the all new badges-team tag.
So long and thanks for all the fish badges!