List view
An attempt to clean out tech debt from the Augur Codebase Tech debt is essentially a nickname for "technical debt", which is essentially a software engineering/developer term for code "mess" that accumulates over time. For example, if part of a codebase (such as a function to insert bulk data into a database, or a logging system) is refactored/rewritten, but not everything that was using the old system got moved over, the code now has two methods for doing that thing. You could also think of technical debt as maybe "shortcuts" that get taken with regard to the code (often done to save time) that need to be cleaned up later. Sort of like "hey ill just do things this way temporarily and fix it later". Its called debt because its similar to "taking out a loan against your future" but for code. Just like how you may get a student loan to pay for university and pay it back later when you get a job, tech debt is similar - you are doing something now that requires some of your time in the future to clean up or do properly. Augur as a codebase started as an academic project (so lots of experimenting was happening) and has also been around for a while and has been through several rewrites. The deeper i dig into the code tha more stuff i find that feels like tech debt (i.e. two functions doing the same things, two different ways to print information to the console - which this PR helps with, etc). Ive been labeling issues that identify tech debt and PRs that help clean up that debt and have made it somewhat of my personal mission, especially this month, to see how much of Augur's tech debt I can clean out. This will: help make it so that its much easier for new people to contribute to and understand the code help me learn the codebase because I'll likely be looking through every part of it reduce the amount of code i need to change for bigger future projects in the upcoming year or so (such as getting gitlab collection working, adding support for Forgejo, etc.)
Due by November 30, 2025•0/11 issues closed- No due date•0/5 issues closed
- Overdue by 9 day(s)•Due by October 31, 2025•8/10 issues closed
UPdating the Augur API to include all possible CHAOSS metrics and metric models
Overdue by 1 year(s)•Due by January 27, 2024- No due date•1/2 issues closed
- Overdue by 1 year(s)•Due by January 27, 2024•6/65 issues closed