Automatically enforce API Compatibility and OSGi Semantic Versioning during builds and code reviews
Writing good software isn't always easy; writing good and versatile open-source software that scales with time, with complexity, with amount and diversity of code authors, while increasing its development speed and keeping a huge ecosystem of extenders healthy for an extremely low to null maintenance cost on adopter's shoulders thanks to backward compatibility is even more challenging.
This is the challenge the Eclipse Platform has successfully faced for soon to be 2 decades, and has made it almost trivial to deal with in the last months.