Members and committers are invited to represent the ASF on JSRs with the purpose of both promoting our values as well as ensuring that the Apache community can continue to influence and participate in the creation of new Java technology. Because participating individuals are representing the Apache Software Foundation (and not themselves), the ASF reserves the right to decide who represents the ASF. The ASF also will work to help individuals join expert groups, as we believe that independent representatives that have a good understanding of the value of open source are important to the health of the JCP communities.

The general guidelines for participation are :

• You represent the interests of the ASF and your particular technical community, and not of your employer or personal technological interests.
• If there is an existing community at the ASF that has an interest in the JSR, engage with your community to bring feedback and ideas to the EG. If not, keep in mind how an ASF community might build or extend such a specification.
• You must sign an Non-Disclosure Agreement with the Apache Software Foundation. as the ASF is a signatory with Sun on behalf of its representatives.

If you are interested in representing the ASF on a new or existing expert group that doesn't have ASF representation, or participating with the existing activities on an expert group, please send email to the JCP open list and indicate your interest.

The following JSRs have active Apache representation. Some groups have an internal mailing list that is used by ASF Members and committers to discuss the progress of the JSR and the ASF's involvement through it's representative(s). The list operates under the rules above for representatives.

Because of the work of the ASF, we are able to legally implement JSRs in open source and distribute under the terms of the Apache License. There have been many successful implementations of JSRs at the ASF, in all areas of Java technology.

Projects are free to implement whatever JSR a project community desires, as long the specification license that you agree to allows open source implementations. All modern JSRs do - the key to knowing is to look to see that the JSR was conducted under "JCP version" 2.5 or above. There are some exceptions, such as J2SE 5 which was conducted under JCP v 2.1 yet licensed under the modern open-source-friendly specification license.

The following projects are implementing one or more JCP specifications :

The following projects have officially tested and passed the TCK for their specific technology :

Whenver a project chooses, it may request access to the TCK for the technology they are implementing. The ASF will work to license, acquire and provide the TCK for the project. The following guidelines apply to working with TCKs at the ASF :

• A project can request access to a TCK by sending email to the JCP open list.
• This TCK is for use only for the purpose of the Apache project, and no other.
• While access to the TCK is left up to the requesting PMC, it is strongly encouraged that access be limited to project committers to avoid the perception that the ASF is being used as a "TCK laundry". We have an excellent record in our handling of the TCK materials, and the good reputation of the ASF is dependent upon PMC oversight in this case.
• Every individual that has access to the TCK materials must have executed a Non-Disclosure Agreement with the ASF. The ASF receieves these materials under the terms of an NDA, and we must take due care in how we handle these materials.

The ASF have licensed the following TCKs :

The following TCKs are in process of being acquired :