Good Morning Everyone,
Just like every team we have technical debt in our work.
I would like your help to try to define what it is for us.
So far, I've come up with the following:
- python3 support/migration
- fedora-messaging schema
- OpenID Connect
What else would we want in there?
In my opinion the biggest struggle we have is too many code bases and we don't have the time or interest to make sure that they are all in good shape. I think that even if we were to spend the next 3 months just focusing on paying back that debt (updating documentation, dependencies, tests etc ) we would come back to our current situation in 1 year or so because we just can't keep up.
In my opinion it would be really good to spend some time looking at all the applications interactions and look at opportunities to reduce these interactions and consolidate features in fewer applications. (this is something that I started when looking at PDC and I still think that ideally we should try to not replace PDC but enhance existing services to provide the features we need.)
If anyone can draw a diagram of all the services we have and how they interact with each other I would be super interested to see that and I think that would be a great start to look at reducing our technical debt.
Looking forward to your thoughts,
infrastructure mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
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://email@example.com