Syntax for method references
Neal Gafter
neal at gafter.com
Thu Oct 27 10:46:20 PDT 2011
On Wed, Oct 26, 2011 at 1:54 PM, Brian Goetz <brian.goetz at oracle.com> wrote:
> There was going to be an announcement when consensus was reached in the EG.
> We're not there yet; "front runner" is my subjective characterization based
> on recent discussions. We've been pretty consistent about relaying syntax
> decisions when they're made; this one isn't made yet.
>
Why should any announcement be necessary when the expert group discussions
are public <http://jcp.org/en/jsr/detail?id=335>?
2.14 Please describe the anticipated working model for the Expert Group
working on developing this specification.
A publicly readable mailing list for expert group communication will be the
primary working model.
2.15 Provide detailed answers to the transparency checklist, making sure to
include URLs as appropriate:
- The public can read the names of the people on the Expert Group.
We intend this to be the case.
- The Expert Group business is regularly reported on a publicly readable
alias.
We intend this to be the case.
- The schedule for the JSR is publicly available, it's current, and I update
it regularly.
We intend this to be the case.
- The public can read/write to a wiki for my JSR.
Rather than a wiki which the Expert Group must take time out to visit, we
intend to implement a pair of mailing lists following the approach of JSR
294 and JSR 330. First, Expert Group business will be carried out on a
mailing list dedicated to Expert Group members. Second, an "observer"
mailing list which anyone may join will receive the traffic of the Expert
Group list. The observer list allows the public to follow Expert Group
business, and is writable to allow the public to make comments for other
observers to see and make further comment on. Expert Group members are under
no obligation to join the observer list and partake in public discussion. In
addition to these lists we will maintain a private Expert-Group-only list
for administrative and other non-technical traffic.
Cheers,
Neal
More information about the lambda-dev
mailing list