Bug Resilience Project: Work Package 1: Lowering Technical Debt in Participating FOSS Projects and fixing known issues
Awarded
The competition has ended and a winner has been selected.
- Qualification deadline
- Jan 9, 2024Expired
- Award
- Leistun, weight 70
Brief
The contractor will develop a working concept based on the following criteria: - Working with participating FOSS infrastructure projects to identify and make an inventory of known issues caused by under-maintenance, including but may not be limited to: - Known bugs or other problems with the codebase that haven"t been addressed due to lack of capacity - Significant technical debt that is caused by lack of maintenance resources - Complexity in the codebase that causes a barrier to long-term maintenance or a threat to the project"s security posture - Missing best practices or structures that could be implemented to enable long term secure maintenance practices. - Develop a roadmap and a work plan to help the projects prioritize and address the known issues that have been identified. - Provided additional capacity, knowledge and code contributions for the projects as needed through: - Providing re-engineering, re-coding, refactoring or removing code services; - Fixing known bugs; - as well as help implementing best practices or standards for future ease of maintenance, such as badge programs or certifications.
Systemutvikling og programmering
Result
- 3Number of tenders received
- Not statedContract value
Previous winners
Who are you up against?
The suppliers who have won similar contracts at SPRIND GmbH
Will you bid?
The agent sets up the bid and writes the first draft. Free for 14 days.
Award Criteria
Source
No source found in the documents. Check the weight against the tender documents.
Source
No source found in the documents. Check the weight against the tender documents.
From the notice
The contractor will develop a working concept based on the following criteria: - Working with participating FOSS infrastructure projects to identify and make an inventory of known issues caused by under-maintenance, including but may not be limited to: - Known bugs or other problems with the codebase that haven"t been addressed due to lack of capacity - Significant technical debt that is caused by lack of maintenance resources - Complexity in the codebase that causes a barrier to long-term maintenance or a threat to the project"s security posture - Missing best practices or structures that could be implemented to enable long term secure maintenance practices. - Develop a roadmap and a work plan to help the projects prioritize and address the known issues that have been identified. - Provided additional capacity, knowledge and code contributions for the projects as needed through: - Providing re-engineering, re-coding, refactoring or removing code services; - Fixing known bugs; - as well as help implementing best practices or standards for future ease of maintenance, such as badge programs or certifications.
Contact
leo.lerch@mazars.de- Result · Framework agreement · PrequalificationType
- Leipzig, Kreisfreie StadtLocation
- 72200000Main codeSoftware programming and consultancy services