Hello, Markus and Werner.
From my understanding talking to many different people, speed of the process surely isn't the main reason this move occurred. It is what is state by Bruno on September's minutes: "Bruno commented that there is a perception for the JCP is an Oracle organization"
Opinions I heard and remember:
- "Oracle was charging people for TCK access on things they contributed to, which is unfair" (and I agree)
- "Oracle has the final say on what's in or out of Java EE, and that's not community oriented" (and I agree)
- "Only Oracle can lead new Java EE umbrellas, and that can lead to situations like the 6-year Java EE hiatus" (and I agree)
- "Many potential contributors are not contributing because it's too close to Oracle" (and I disagree on the reason they're not contributing, but I may be wrong)
- "Many potential contributors are not comfortable signing the JSPA" (and I'd agree)
- "The need for standardization in this OSS age are not as needed as before, so it's better to evolve thing outside of a standards body" (which has some merit but is a bogus reason)
So, the move of placing the Java EE technology under EE4J removes most, if not all, potential barrier for tech evolution. Other Java related techs (like Java ME and SE) have their own needs and evolutions, and each is going thru their "rethinking" - I'm leading the one for Java ME, and Java SE move to release train shows that rethinking is happening too.
Regards,