On Sat, Aug 31, 2013 at 12:07 AM, Ed Merks <[email protected]> wrote:
> John, > > Please me be equally provocative. > Hi everyone, before we declare thermonuclear war on each other, let's take a step back. John, there is no doubt that the success of Eclipse is a result of vibrant eco-system that has grown-up around the platform. The successful Eclipse projects that build on the platform are just as important as the core. I would argue that EMF (and Ed Merks in particular) is not simply an 'Eclipse Adopter'. In fact, I would say Ed has set the gold standard for Eclipse development. Ed, John is 100% correct that the project committers get the final say for all decisions. This is not just *how* it works, it's how it *must* work. Eclipse is a meritocracy, and John Arthorne has certainly earned the right to make any decisions regarding the core API -- and I don't think you could find anybody here that would disagree with that. John has gone above and beyond everyone else to ensure that the Eclipse Platform continually ships quality code, on-time. So, where do we go when two well-respected members of the Eclipse community have a different view of a core component that is shared between them? I wonder if the Architecture Council could play a role here? I don't think there is currently any precedent for this, but Wayne is re-working some of the EDP and maybe the AC should be given some power to actually 'architect' when different opinions emerge? Thoughts.... Finally, I want to call out Hendrik (the GSoC student working on this). I'm not in any position to judge your work this summer, but as a former GSoC student I couldn't imagine finding myself in a position such as this. Please don't let this little schism discourage you. Cheers, Ian
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
