Adopt a JSR Program
This program is intended to encourage JUG members to get involved in a Java Specification Request (JSR) and to evangelise that JSR to their JUG and the wider Java community in order to increase grass roots participation. JSRs cover all aspects of the Java ecosystem such as the new Date and Time API coming into Java 8, the latest JavaEE 7 APIs for the cloud and much more! This program will realise the following benefits:
The benefits to JUGs and individual members adopting a JSR are hopefully obvious. It looks great on the CV, gives you new technical and community skills and much more!
With JSR-348 bringing openness and transparency to the way in which JSRs are run, this is a great opportunity for all of us to help the Java ecosystem thrive.
An overall guideline for this program is that we want to gather up the enthusiasm and skill sets of Java developers around the world, but then focus their efforts at specific areas within JSRs. For example, this means that for the latest complex language features in Java 8 we'll encourage most 'Adopt a JSR' members to try the latest builds, evangelise the betas to major open source projects and to provide feedback on day-to-day usage. A smaller number of JUG members who are really qualified in the area of language design (if you think syntax is the important bit, then this probably isn't you) will be encouraged to contribute more directly. This of course includes enthusiasts who are willing to put in the time to really learn about this stuff. As Yara from SouJava pointed out at Devoxx, this is a great opportunity to also mentor budding experts in the various JSRs, so that there is a path for those who want to travel it.
Any time you need help please mail the JUG leaders list
See Managing the Adopt a JSR program to go forward from there!
The Grids below indicate which JUGs are working or have worked on a JSR.
NOTE: Multiple JUGs can and should collaborate on a particular JSR! there's always plenty of work to do and it can be easily distributed.
|JUG||JSR-310 (Date and Time)||JSR-321 (Trusted Computing)||JSR-331 (Constraints Programming)||JSR 335 (Lambda Expressions)||JSR 339 (JAX-RS 2.0)||JSR-343 (JMS 2.0)||JSR 344 (JSF 2.2)||JSR 346 (CDI 1.1)||JSR-347 (Data Grids)||JSR-349 (Bean Validation 1.1)||JSR-350 (Session State management)||JSR-351 (Identity Management)||JSR-352 (Batch processing)||JSR-353 (JSON API)|
|LJC||310 Page||335 Link TBA||339 Link TBA||346 Link TBA||347 Link TBA||353 Link TBA|
|SouJava||310 Link TBA||335 Link TBA||339 Link TBA||344 Link TBA||349 Link TBA||352 Link TBA||353 Link TBA|
Every JUG will want to work differently, all we can suggest is that you put together a wiki similar to LJC's Adopt a JSR Program and for each JSR, a wiki similar to LJC's Adoption page for JSR-310 - New Date and Time.
This section (taken from Somay Nakhal's work) contains some guidance for JUG members who are leading an Adopt a JSR group as used by the LJC. Take as much or as little of it as you need!
Once a group has really gotten going the leader(s) of the Adopt a JSR group might find it useful to:
Some other miscellaneous things you can do are:
In London each little group does it their own way, some meet F2F, some do it over email, others have Skype sessions. Whatever way works with your group is fine.
The tasks that we deal with in London typically fall into two categories:
Each JSR should run its own infrastructure (the Spec lead / EG will have the details), the Adopt a JSR volunteers should simply use that.
You'll find the deadlines on the official JSR page at JCP.org for each JSR. The LJC and the JCP.org folks are working on a calendar that can be shared that has these dates on it.
Again, any questions, comments etc send to the JUG leaders list
Back to Home