Doug Lea leaves the JCP
By Henrik Stahl on Oct 25, 2010
Doug Lea recently announced his intention of leaving the JCP Executive Committee and posted a public letter outlining his reasons which you can find here.
Doug is a professor of Computer Science at the State University of New York and has been a prominent independent member of the Java community for a very long time, leading efforts in areas such as Java concurrency. I know that we at Oracle - the Sun Java team, the BEA JRockit team and many Java users in Oracle's software division - greatly value his contributions. I am sad to hear that he has decided to leave the JCP EC, and can only say that I hope that he will still continue to act as a leader in the community. People like Doug are needed to balance the priorities and interests of Oracle and other big corporations.
Doug and a few other members of the community such as Stephen Colbourne have made some very strong statements regarding the JCP. Needless to say, we don't agree with this bleak description of reality. We believe that the JCP is and remains a good organization for ushering the Java standards forward. We agree with the need of continually improving the JCP, and will work on that together with the EC. We also note that the EC contains a diverse set of companies and individuals, many of which are among Oracle's most fierce competitors. We believe that an open, vigorous and sometimes heated debate between conflicting interests and differing opinions is a necessary part of hammering out standards that serve the best interests of Java users, and we are confident that a vast majority of the EC members agree with us on this.
Regarding the JCP, we will very soon submit JSRs for Java SE 7 and 8. And - assuming the EC approves the submissions - will work with other JSR Expert Group members on the details of these specifications.
Doug - If you read this - I am sorry that we have not met in person yet and I hope we can rectify that at some point in the not too distant future. I have a personal goal of making Oracle's decision process around our view on the Java roadmap and our implementation more transparent and predictable and would love to get your input on how to accomplish that.