The Grids below indicate which JUGs, individuals and organisations are working (or have worked on) JSRs.
NOTE: Multiple JUGs, individuals and organisations can and should collaborate on a particular JSR! there's always plenty of work to do and it can be easily distributed.
21 separate JUGs have already joined!
Belgium JUG, Campinas JUG, CEJUG, Chennai JUG, Cologne JUG, Congo JUG, Faso JUG, Guadalajara JUG, Houston JUG, Hyderabad JUG, Indonesia JUG, Istanbul JUG, Joglo Semar JUG, Jozi JUG, LJC, Madrid JUG, MBale JUG, Morocco JUG, Peru JUG, SouJava JUG, Silicon Valley JUG, Toronto JUG
It's very important that any Adopt a JSR efforts are co-ordinated with with the Spec Leads / EG!
The best way to call for volunteers is to mail the [email@example.com members list]. After that, each JUG, individual or organisation in the 'Who Is Adopting JSRs' matrix should ideally join the existing mailing lists etc that the JSR already has in place to co-ordinate work. We've made some suggestions (see What to work on for a JSR) as to what work an Adopt a JSR group can work on, but would love to hear more ideas!
These JSRs are currently going through the Java Community Process (JCP) in order to become a ratified standard. It's a great time to get involved in these early to help shape the future!
(JCACHE - Java Temporary Caching API)
(Date and Time)
(Content Repository 2.1)
|Guadalajara JUG||JSR 310|
|JoziJUG||JSR 310||JSR 335|
|Hyderabad JUG||Hyderabad JUG|
|LJC||107 Page||308 Page||310 Page||335 Page|
|SouJava||310 Link TBA||335 Link TBA|
(ME Embedded Profile)
These JSRs are now ratified standards - but there's plenty you can still help with such as educational efforts, working on implementations, helping with the next revision etc. See Live JSRs
See Closed JSRs
Back to Home