The Community Platform Engineering team (formerly Community Infrastructure) indicated in July of 2019 that they have a higher workload than the team can bear. To ease this, they evaluated the applications that fit their mission statement. The applications that didn’t fit the mission were proposed for hand off to the community.
I am happy to say there is a lot being done to preserve the applications that our community values. I have been working with the Fedora Project Leader (FPL), Fedora Program Manager (FPgM), Community Platform Engineering team (CPE), and the Open Source Program Office (OSPO) at Red Hat to transition app hosting and maintenance from CPE to OSPO.
These applications store data protected by GDPR and are therefore required to continue to be hosted with Red Hat. Once we were notified that this was the case, we went to work on finding a new place for the applications to live, with OSPO being the obvious choice. Currently, OSPO is evaluating the list of applications to see exactly what they are able to provide for our community.
I have been facilitating things with the specific people whose these responsibilities will end up falling on. The confirmation that this plan would be followed through was secured in the last couple weeks. I truly hope that folks are going to be happy with what we have all been working to accomplish.
Moving forward, the plan is to address things based on need. The first thing we decided to work on is Fedora Badges (really, it was going to break in half so we saved it, thanks Badges crew!). We all LOVE Badges, and I know many would be sad to see this go. That is why we are sponsoring a Fedora Badges Back-End Engineering intern for this upcoming session of Outreachy running May 19th–August 18th. The goal is to have Fedora Badges revamped by the end of the summer and hosted with OSPO.
Breakdown of the process:
- CPE presented a list of apps of selected applications they wanted to hand to the community with a long term schedule
- Individuals started to make efforts to make plans for apps of interest (for example I had a badges hackfest last year at Flock to work on a solution for this exact topic)
- Things were put on hold until GDPR’s impact was more clearly defined
- Meetings between the FPL, FPgM, and FCAIC to review each app/tool line by line, looking at a variety of qualifications. For example: use case, scale of need, is it currently being maintained/developed, does it *have* to be this particular solution, is there personal data to be taken into account.
- From there we proposed owners for the apps. At this point, we have presented OSPO with a list of apps and they are evaluating their needs from CPE to effectively transition them over. From here, the idea is for OSPO to move each app over one by one.
I hope this helps shed some light on what we have been working on. The best way to get involved is to stay up on further communications and keep pitching in to improve your favorite community apps. Keep using and contributing to the apps as you normally would and we will do our best to communicate outages or future plans. The work OSPO is going to take on is focused on maintenance versus development. They are happy to support continued community development.
These are the things that we hope to move to OSPO’s administration:
- Badges stack – Fedbadges, tahrir, tahrir-api
- Fedora Packages
- Mailman stack – Mailman-core, postorius, hyperkitty
Stay safe and healthy, Fedora!