Java Tools

Java Tools Community -- JCP Relationship Guidelines

The Java Tools Community (JTC) is dedicated to the advancement of Java Community Standards in the area of development toolability and tool interoperability. Toolability is the measurement of how easy it is to build tools around a particular standard or technology. In order to succeed at this goal it is imperative that the relationship between the JTC and the Java Community Process (JCP) be open, active and productive. The following statements are intended to outline the different components of this relationship. site bouwen

JTC Initiatives

It will be encouraged for the JTC to initiate new JSRs in the area of Java development tools and frameworks. Any JTC member can present an idea to the JTC for consideration as a standards proposal. If the JTC decides (via a vote¹) to accept the proposal, a sub-committee will be formed to discuss, outline and describe the technology use cases for JSR submission.

The member submitting the original proposal will determine who will take ownership of the submission, including specification lead, reference implementation and TCK. The JTC will never have ownership of any JSR, technology or IP. Once the proposal is completed a single JCP member will submit the JSR using the norma l, existing JCP process. The JTC will decide by its consensus which member submits the JSR. Once the JSR has been submitted, the JTC will follow the lifecycle guidelines outlined below. Games online, dress up games for free.

If the JTC decides to decline supporting the proposal, the member(s) who presented the proposal may still opt to submit the JSR to the JCP using normal channels, but without the approval and support of the JTC.

Expert Group Liaison

For each new Java Specification Request (JSR) that the JTC determines has an impact, either directly or indirectly on development and development tools the JTC will ensure that at least one member of the JTC is also a member of the expert group of the JSR. This will ensure that the JTC has a voice and awareness in tools-related JSRs and will help ensure that design-time requirements and issues are considered and implemented in the standard interfaces. Play racing car games for kids online.

For JSRs where the JTC has no representation on the expert group, JCP 2.6 adds additional transparency by allowing expert groups to publish a publicly available Early Draft that JTC members can review and discuss.

Note: It is desired for the EG domain-specific Liaison to be a more formal role in the JCP process. The JTC will work with the JCP in the future to try and formalize such a role.

Lifecycle of a JSR

Once a Java Specification Request (JSR) enters the JCP lifecycle only JTC members who have joined the JSR expert group will have access to the expert group discussions. However for each JSR the JTC will have a dedicated email list whe re JTC members can discuss ideas and thoughts about the JSR independently of the expert group discussions. JTC members who are also on the JSR expert group can use this JTC mailing list to get ideas and insights into how the community views issues related to the JSR, but may not divulge any information from the expert group discussions that would violate the policies or practices of the JCP.

Once the JSR enters back into the public domain through one of the review periods, all JTC members are encouraged to use the JTC JSR mailing list to discuss and collect issues relating to the JSR, and then form collective feedback to the expert group. It is encouraged that any JTC member who is also a member of the JSR expert group would provide a summary and initial guidance to the JTC on a JSR entering public review that would outline any possible tools-related issues contain in the JSR.

Endorsement

At the time of any public review of the JSR process the JTC may decide via a vote to either approve or disapprove of a JSR. If they approve of a JSR, a supportive term, such as "JTC Endorsed" will be associated with that JSR to let the industry know that the JTC has considered and approves of that JSR. A list of approvals and disapprovals can be found on the website. Some things that will be taken into account in this process will be:

JSRs impact on development tools and toolability
JSRs impact on runtime frameworks
License terms presented in the JSR proposal
Etc.

Note: The JTC approval process of a JSR has no bearing or binding on a member's JCP Executive Committee (EC) vote on the same JSR. For example, a company may desire to vote differently in the EC vote than the JTC vote.

Member Commentary

A portion of the JTC website will be dedicated to member feedback and commentary on the different JSRs. This can be in the form of:

Email lists for general discussions as well as email lists dedicated to a particular JSR technology.
Forums, where any member can bring up ideas for tool-related technology. Any thoughts on existing JSR-related technology would be addressed in the observer mailing list for that JSR.
Statement of positions by the different members. This will allow for any member to publicly state support or disapproval of a JSR regardless of the JTC position. Statement of positions may be associated and linked to/from a particular JSR's approval or disapproval decision page.

1) The process for voting and decision-making in the JTC will be outlined in a separate document. For the purpose of this document it is assumed that such a process is in place and that final decisions can be made.

(Page last updated 6 January 2004)