Brian Goetz, Java Language Architect at Oracle and specification lead for the Lambda expressions project, has announced that mailing lists for JSR 335 will be made publicly available.
After long delays involving far too many meetings with lawyers, I am pleased to announce that we are ready to make the JSR-335 EG lists publicly readable. This is a key milestone in the transition to the JCP 2.8 process which offers greater transparency into the evolution of the Java platform.
Two new lists will be created, one for the language specification work, and one for the libraries specification work. Each will have three sublists:
- A list for the expert group. The archives are public, and only the EG members can subscribe and post.
- An observers list - traffic sent to the EG list will be copied here, and anyone can subscribe. EG members may or may not participate on this list, at their choosing.
- A comments list - acting like a suggestion box, comments sent here will be considered for expert group discussion.
There is also a private list for the expert group, which is primarily used for confidential logistical discussions, exchanging personal contact information and so on.
A couple of days before the announcement Stephen Colebourne, lead of the JSR 310 Date and Time API, expressed his frustration at the lack of progress, on a blog post
Back in October last year, I wrote about the lack of access to the expert group mailing list of Project lambda, the effort adding closures to JDK 8. Has anything changed? Well of course not.....After years of asking, there still is no publicly readable mailing list for the expert group.
Reaction to the move has been universally positive, with Colebourne himself writing
While I may occasionally be publicly grumpy, it's great to see a positive end result for this JSR. Thanks for making it happen.
Others joined in, including Neal Gafter, Ben Evans, and Martijn Verburg, co-lead of the London JUG, who tweeted
Well done to @BrianGoetz et al for getting #jsr335 mailing lists opened up - transparency & openness in #java is good.
Progression towards adopting newer, more transparent, versions of the JCP process has been slow, with so far only a smattering of JSRs, mostly focused on Java EE 7 and reforming the JCP itself, using version 2.8 of the process. It is though good to see some progress, particularly with a specification change as far reaching as lambda expressions could be to the Java language.
Community comments
Kafkian
by Néstor Sánchez,
Re: Kafkian
by Javier Diaz,
Re: Kafkian
by Cameron Purdy,
Re: Kafkian
by William Smith,
Re: Kafkian
by Néstor Sánchez,
Kafkian
by Néstor Sánchez,
Your message is awaiting moderation. Thank you for participating in the discussion.
This is incredible: Instead of announcing or launching a product this article shows (as a great event) the public exposure of a "mailing list"!
Is this a bureaucratic ceremony of the stalinist soviet union or what?
Re: Kafkian
by Javier Diaz,
Your message is awaiting moderation. Thank you for participating in the discussion.
I'm not sure if your question is rhetorical ... It seems that Java 8 may not have modularity but may be specified openly (which I consider as progress after all the Apache-Google "business" in recent years). This is not about PRODUCTS, but PROCESS!
Re: Kafkian
by Cameron Purdy,
Your message is awaiting moderation. Thank you for participating in the discussion.
Nestor -
Oracle has (perhaps quite unexpectedly!) been driving a campaign to open up the JCP, get transparency into the process, etc. This was started in JSR-348: jcp.org/en/jsr/detail?id=348
While Brian says that he had lots of meetings with lawyers, it's worth noting that it was Oracle pushing for the openness, and the obstacles to opening up the process were mostly external to Oracle -- including at least one party that was publicly bashing Oracle while privately blocking the mailing lists from being made public.
While I don't know that this story is worth headlining on InfoQ.com, it is actually a very positive sign of progress in getting better transparency into the JCP, and yet another sign that Oracle is acting as a responsible steward of Java. There's still lots of work to be done, and the successful delivery of Java SE 8 and Java EE 7 is only part of the picture.
Peace,
Cameron Purdy
(Working at Oracle but these are my own personal opinions.)
Re: Kafkian
by William Smith,
Your message is awaiting moderation. Thank you for participating in the discussion.
Many of us Java developers have been pushing for more transparancy in/influence over how Java evolves for many years. This is a small thing but good news, and deserves to be celebrated as such.
Re: Kafkian
by Néstor Sánchez,
Your message is awaiting moderation. Thank you for participating in the discussion.
I see, guys. I was just perplexed. Sorry for the sarcasm.