JSR #203 More New I/O APIs for the JavaTM Platform ("NIO.2")
The materials on this page are provided by the Spec Lead of this JSR for evaluation and feedback.
These materials are not final, and are subject to change as the JSR progresses through the process.
JSR 203 transparency survey, from April 2009:
> - Are you using a public mailing list for the JSR--using the observer alias provided by the JCP No. > - Are you using a public mailing list for the JSR--using other means than provided by the JCP (if so, is this read-only or read/write?) We have two mailing lists that anyone can subscribe to (read/write): email@example.com firstname.lastname@example.org > - Are you hosting a spec lead blog with frequent updates on activity in the JSR Not until recently: http://blogs.sun.com/alanb/entry/jsr_203_nio2_update > - Are you providing accurate, public schedule for the JSR on jcp.org or elsewhere Yes, the project page (http://openjdk.java.net/projects/nio) has a "Status" section that I keep up to date on the current status/plans. > - Are you using the JCP Community Update page for your JSR on jcp.org No > - Are you hosting development of the spec, RI, or TCK on a collaboration website such as java.net or sourceforge All development is being done here: http://openjdk.java.net/projects/nio The project page has links to the latest javadoc, source code, binaries and other resources. > - Are you making regular (~ monthly) public drafts available in between the formal JCP stages (Early Draft Review, Public Review, Proposed Final Draft, etc) Yes, every 4-6 weeks. Also, jdk7 early access downloads. > - Are you using lightweight technologies like Twitter for quick update messages and allow broad following of the JSR No. > - Are you releasing a public list of the names of the individual participant members on the expert group http://openjdk.java.net/projects/nio/acknowledgements.html > - Are you making all JSR feedback accessible to the expert group Yes, all feedback to jsr203-comments has been forwarded to the EG. All feedback to nio-dev or nio-discuss is accessible to anyone. > - Are you using public issue-tracking No. > - Are you using discussion forums or Wikis No. > - Are you utilizing open-source development processes for the RI or TCK For RI (not TCK because this API is planned to be a component of Java SE 7 and thus the TCK development is part of JCK7). > - Are you doing anything else (speaking at conferences, etc)? JavaOne, Google Talks, and others have presented the API at other conferences (Devoxx, ApacheCon, ...).