> We all know that the root cause of this discussion is the 10+ years of under-resourcing for Eclipse platform.
Eclipse Platform is not under-resourced. It's OK-resourced, and just like any project would benefit from more resources, but let's move the resources discussion away and focus on the community aspects of auto-closing bugs. > Do we expect big players to come back and sponsor teams of developers again as it was in 00ths? I doubt so. Perhaps, small companies and individuals from the community are the only hope. I don't get how it's related to the discussion about auto-closing bugs or not. And I also don't get how Alex's answer triggered that question. And if yes, how auto-close could help to recruit new resources for > triaging (not even dreaming about bug fixing) from the community? Auto-closing is more likely to stimulate people in trying to contribute than just keeping the bug silent. At least, people can decide to reopen with more details, or to add other information (not useful anymore, was fixed), and that's a form of contribution already. Sometimes they reopen with frustration and this can trigger a new conversation with some committers to help them in contributing more. On the other hand, keeping the bugs open but silent brings no interaction and thus no new opportunity to recruit. It just make the project seem dead.
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
