Software can and should be considered 'completed' once it fulfills its value proposition. Rather than treating low commit frequency as a sign of abandonment, it should be seen as a sign of maturity and stability. Projects like Sway and scdoc demonstrate this philosophy — by drawing a finish line on new features and focusing only on bug fixes and robustness, maintainers can deliver software that 'just works'. Managing change is key to reliability: every new feature or external dependency update risks introducing new bugs. Maintainers should critically evaluate feature requests based on their cost to complexity and stability.
Sort: