Who's Adopting JSRs?

Version 27

        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.


    Overall List

        36 separate JUGs have already joined!

        Belgium JUG, Bucharest JUG, Campinas JUG, CEJUG, Chennai JUG, Chicago JUG, CLOJUG, Cologne JUG, Congo JUG, Detroit JUG, EGJUG, Faso JUG, Guadalajara JUG, GUJavaSC, Houston JUG, Hyderabad JUG, Indonesia JUG, Istanbul JUG, Japan JUG, Java Hellenic User Group, Joglo Semar JUG, Jozi JUG, London Java Community (LJC), Madras JUG, Madrid JUG, MBale JUG, Medellin JUG, Morocco JUG, Netherlands JUG, Peru JUG, Philadelphia JUG, PT.JUG, Silicon Valley JUG, SouJava JUG, Toronto JUG, Ukraine JUG, .




    JSRs in progress


    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!

    <= #340


    (Safety Critical)
    (Content Repository 2.1)


    #340 --> #369


    JSR 362
    (Portlet 3.0)
    JSR 363
    (Units of Measurement)
    JSR 365
    (CDI 2.0)
    JSR 366
    (Java EE 8)
    JSR 367
    JSR 368
    (JMS 2.1)
    JSR 369
    (Servlet 4.0)
    CJUGJSR 366
    Chennai JUGJSR 363
    EGJUGJSR 363JSR 366JSR 367JSR 368
    Guadalajara JUGJSR 367
    GUJavaSCJSR 365JSR 369
    Hyderabad JUGJSR 363
    Java Hellenic User Group - JHUGJSR 366
    LJCJSR 363JSR 365JSR 366JSR 367JSR 368
    MoroccoJUGJSR 363JSR 365JSR 367JSR 369
    Peru JUGJSR 366JSR 367JSR 369
    Philly JUGJSR 366JSR 368JSR 369
    SouJavaJSR 363
    Ukraine JUGJSR 367


    >= #370


    JSR 370
    (JAX-RS 2.1)
    JSR 371
    (MVC 1.0)
    JSR 372
    (JSF 2.3)

    JSR 373

    (Java EE
    Mgmt 2.0)

    JSR 374

    (JSONP 1.1)

    JSR 375

    (Java EE

    JSR 376


    JSR 377

    (Desktop / Embedded

    JSR 378

    (Portlet 3.0 Bridge

    for JSF 2.0)

    JSR 379

    (Java 9)

    JSR 380

    (Bean Validation 2.0)

    Bucharest JUGJSR 374
    Detroit JUGJSR 379
    EGJUGJSR 371JSR 372
    Guadalajara JUGJSR 370
    GUJavaSCJSR 370JSR 371
    Japan Java User Group - JJUGJSR 371
    Java Hellenic User Group - JHUGJSR 371
    LJCJSR 370JSR 371JSR 379
    Madras JUGJSR 374
    Medellin JUGJSR 380
    MoroccoJUGJSR 370JSR 371
    Netherlands JUGJSR 371JSR 379
    Peru JUGJSR 371JSR 374JSR 375JSR 379
    Philly JUGJSR 375JSR 379


    Live JSRs

    See Live (Completed) JSRs - 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.

    Closed JSRs

    See Withdrawn or Rejected (Closed) JSRs

    A Note for Spec Leads / EG members

    It's very important that any Adopt a JSR efforts are coordinated with with the Spec Leads / EG!

    The best way to call for volunteers is to mail the [adopt-a-jsr@googlegroups.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 JSR) as to what work an Adopt a JSR group can work on, but would love to hear more ideas!