Adopt-a-JSR for Java EE 7

Adopt-a-JSR is an initiative by JUG leaders to encourage JUG members to get involved in a JSR and to evangelize that JSR to their JUG and the wider Java community, in order to increase grass roots participation. Java EE 7 is scheduled to release in Q2 2013 and would love help from your JUG to adopt a JSR.

The typical question in Adopt-a-JSR is "how do I get started ?".

In general, the Starter Level tasks are helpful at all stages of a JSR. For the Java EE 7 platform, a comprehensive feedback on each JSR is always appreciated. However the JSRs are in different stages and require different level of help. The recommended areas for providing feedback for each JSR is listed below.

Java API for Temporary Caching 1.0 (JSR 107)
Concurrency Utilities for Java EE 1.0 (JSR 236)
Java Persistence API 2.1 (JSR 338)
Java API for RESTful Web Services 2.0 (JSR 339)
Servlet 3.1 (JSR 340)
Expression Language 3.0 (JSR 341)
Java Message Service 2.0 (JSR 343)
JavaServer Faces 2.2 (JSR 344)
Enterprise JavaBeans 3.2 (JSR 345)
Contexts and Dependency Injection 1.1 (JSR 346)
Bean Validation 1.1 (JSR 349)
Batch Applications for the Java Platform 1.0 (JSR 352)
Java API for JSON Processing 1.0 (JSR 353)
Java API for WebSocket 1.0 (JSR 356)
Java Transaction API 1.2 (JSR 907)

General Areas for Providing Feedback

Each specification can take general feedback in the following areas:

Download and review the latest version of the specification (available from the JSR page or the corresponding java.net project). You don't need to necessarily review the entire specification and instead can focus on specific chapters and sections.
Download and review the javadocs for clarity and completeness.
Build sample applications using the implementations integrated in GlassFish 4.
Explore integration of one/multiple technologies with your existing Java EE applications.
File bugs on the corresponding spec or RI project.

These areas can be applied for the specifications that do not have any specific areas identified.

Guidelines for Providing Feedback

These are general guidelines for providing feedback. The specification lead and the Expert Group has the final decision on incorporating the feedback.

For specifications in Public Drafts, new feature requests may not be considered for this release. For specifications in Early Draft, new features will only be accepted if they are within the existing scope. If new features are not accepted for this release, then they will get tagged for the next release.
Multiple JUGs can and should collaborate on a particular JSR. There is always plenty of work and going through the material multiple times only makes it that more better.
When communicating with the EG, its recommended to include "Adopt-a-JSR" in the subject line.
When filing a JIRA issue, use "adoptajsr" tag.

How to Participate ?

The following one time activities will allow to collaborate with other JUGs participating in Adopt-a-JSR program.

Join the Adopt-a-JSR program and subscribe to members@adoptajsr.java.net (archive).
Update the wiki to indicate your interest in a particular JSR by creating a page.
Communicate directly with the specification lead or the java.net users alias for the specification.

Getting Started with Java EE 7

Participating JUGs