Let me start by rejecting your attempt of framing Orbit benefits by using "hypothetical" as well as denying all the successful, fruitful and helpful collaboration in Orbit which happened in the past and still happens today.
So if those benefits are not hypothetical, please answer to this question I have to ask again: how would publishing slf4j 2.0 to Orbit would have prevented this issue in m2e? As long as there is no good answer to that, I don't think requesting Platform committers to do extra work for Orbit when better workflows were identified has any chance to be successful.
You're asking Platform committers to do basically spend much more time for some tasks, so what's the concrete value to expect in exchange of this extra effort? The slf4j 2.0 vs m2e bug is a concrete opportunity to emphasize how Orbit can avoid issues and increase quality/collaboration and so on. So please use this opportunity to build a case in favor of Orbit by explicating how Orbit would have prevented this issue from happening.
If you're not successful in building such a case, then we'll gladly let you join the club of those who think Orbit is not so profitable as it used to and that the future can be brighter without Orbit ;)
