Responsibly Abandoning Open Source Projects - Jason Turner - NDC Copenhagen 2026
This talk outlines best practices for developing and maintaining open-source projects to ensure they can be responsibly abandoned or handed off years later without becoming 'legacy' or 'abandoned.' The core focus is on achieving a state of 'completeness' by implementing rigorous automation across the entire development lifecycle—from static analysis and comprehensive testing (including path coverage, fuzzing, and mutation testing) to simplified build processes. Key recommendations include automating all quality gates within CI/CD pipelines and minimizing technical debt related to tooling complexity.
Key takeaways
-
Achieve 'Completed,' Not 'Abandoned'
20:30
When concluding work on a project, aim for the status of 'completed' rather than 'abandoned.' This requires proactive measures like maintaining clear documentation and ensuring continuous automation.
-
Automate All Quality Gates
29:55
Implement automated checks for every possible tool (static analysis, dynamic analysis, formatting) to ensure consistency and reduce friction for future maintainers. This should be fully integrated into the build process.
-
Prioritize Strong Typing
34:45
Adopting strongly typed systems (e.g., using type hints in Python or dedicated types like `Point` and `Color`) makes code less prone to order-of-operations errors, significantly improving robustness.
-
Minimize Build Setup Friction
32:10
A new contributor should be able to set up the development environment and run all tests/analysis in a minimal number of steps (ideally five lines or less).