You may already know that individual developers can join the JCP program FREE of change.  Currently about 70 percent of the JCP membership is comprised of this category of members.  Did you know that this extends and includes student developers?  During the month of May, there is extra incentive for students to get involved and participate in the JCP program. The first 20 students to join the JCP program in May 2009 will receive a 1 GB JCP program memory key (note "student" as title on JSPA).

Another growing group of members (currently 2-3%) in the JCP program are institutions and not-for-profits, including Java User Groups (JUG).  The regular $2000 annual fee is being waived for JUGs.
That's right--JUGs can join the JCP for free. Act now !

So far, in 2009, the following JUGs have joined: JUG-USA, Houston JUG, Connecticut JUG, Oklahoma City JUG, Detroit JUG, Malasia JUG, Polish JUG, Japan JUG, Riviera JUG, JUG-RU, JUG-Macedonna, JUG-Utah, JUG-RIO, JUG-WUG (London), JUG-Duchess.  Our inaugural JUG members are SouJava and BeJUG.

There will be a JUG leader meeting with members of the JCP program office on the evening of Monday, June 1 in San Francisco (the day prior to the JavaOne conference).  We want to know how we can better meet the needs of your membership and offer the support you want.  If you are interested please contact me via email at heather at jcp dot org or leave a comment on this blog.  Details are here.  If you can't make the meeting, please get in touch anyway!

A reminder for all JCP program members there is a special discount throughout 2009 for Java training classes in the Sun catalog. You will get your priority code after you join...if you need yours, contact the PMO.

• 10% discount on classroom training
• 25% discount on CD-ROM and web-based training

It's just over two weeks until the 2009 JavaOne Conference.  The JCP program office is busy planning some of the regular favorite events for the community, including the annual party on Tuesday June 2--the annual awards will be presented and Duke will be there.  Check out the details here...more to come as we get closer to June.

Some of the most recent headlines on the JCP program are below.

* [LOTD] CMIS Plugfest, JCR and Star Spec Leads -- Content Management Collection, 5/4

* JCP Program Unveils 2009 Star Spec Leads: Program recognizes Spec Leads who consistently showcase their value -- Sys-Con, 5/2 (Also in Sys-Con Open Source Magazine)

* JCP Announces 2009 Star Spec Leads -- Java Entrepreneur, 5/1

* The JCP up close and personal -- JavaWorld, 4/10

 *HOnline Interview with Patrick Curran, JCP Chair:
http://www.h-online.com/open/Interview-Patrick-Curran-chair-of-the-JCP--/features/112862

The JCP Executive Committee heads to London/Winchester, United Kingdom this week for the second face to face meeting of the year and a press round table.  Look for updates on jcp.org.

JSR 215, JCP version 2.6, is open for Maintenance Review until 25 May.  As previously mentioned, the JCP Executive Committee (as the Expert Group) and the JCP Chair (as the Spec Lead) have been working and discussing these changes for many months.  Once accepted, JCP version 2.7 will take effect in June 2009.  All community spec leads, expert group members, participants, observers, etc are encouraged to review and comment on the proposed maintenance changes.  Send comments to jsr-215-comments at jcp dot org.

You can use the following list to track the changes--it indicates where in the Process document there are edits for each proposal. This is intended to be read along with the edited version of the Process document (see link above).

1. Transparency – JSR EGs must publish and respond to public comments and EC sees it before EC Ballots.
Section 1.2 – there already is a requirement for making JSR initiation comments publicly available and also available to the EC (it's currently ignored). Changed text to allow consolidating similar comments.
Section 2.3 – add words to make same requirement for making comments public in Early Draft
Review as already required in JSR Initiation. Added wording to require publicly viewable response before moving to next stage (Public Draft).
Section 3.1 – add words to make same requirement for making comments public in Public Draft
Review as already required in JSR Initiation. Added wording to require publicly viewable response before moving to next stage (Proposed Final Draft).

2. Transparency - Require publication of full public spec, TCK and RI licenses starting at JSR initiation Section 1.2.1 already says “The Spec Lead will provide the EC with the terms under which the RI and TCK will be licensed no later than the start of JSR Review.” (currently ignored – spec leads often provide a sketch of some terms and sometimes virtually no useful information). Added clarification to require publicly viewable licenses.
Section 2.2.1 same wording as 1.2.1 in section on updates to the information at later stages.

3. Transparency – JSR EGs must publicly state what transparency techniques are used in JSR EG on public JSR status page.
Section 2.2.1 remove words “are free to operate Expert Groups in whatever style they feel is most appropriate”. There are restrictions in the Process doc on how the EGs operate – not useful or accurate to have a statement like this – they can operate according to what the Process document says.
Section 2.2.1 added words requiring that JSR EG must publicly state which transparency techniques are used in the JSR EG. It already says “the EC members expect Spec Leads to carefully choose which tools are best for their Expert Groups and commit to using them” This clarifies that to provide specific information that must be provided about what methods are being used.

4. Transparency – JSR EGs discouraged from using JCP Confidential information in their drafts or final output.
Section 2.1.1 added words to discourage use of information that falls under the JCP Confidential
definition in any EG drafts or output. Using confidential information in EGs prevents use of the other transparency methods. e.g. read only mail lists for EG work, open source groups able to keep up with drafts in implementations.

5. Agility - Clarify process to remove uncooperative spec lead to deal with issues like bankruptcy or other issues that stall the JSR.
Section 2.1.3 added words to allow changing to different JCP Member, not just different person within the same JCP Member organization. The current wording says “the EC may direct the PMO to ask the Member who provided the Spec Lead to provide a replacement”. What does that mean when the Member is an individual? What does it mean when the Member is in bankruptcy and has no ability to act on it? What does it mean when the objectionable behavior from the Spec Lead is a reflection of the lack of interest of the Member or where the Spec Lead wants to stall the JSR?

6. Agility - Clarify role of EG members during Maintenance phase.
Section 3.5 – added words to clarify that Maintenance Lead can call upon members of the EG for aid in the Maintenance role. Did not remove words “and disbands”. The change reflects what actually is the practice now without removing the words. The EG disbands but the Maintenance Lead can continue to call on those members for help (e.g. in preparing a new JSR for a new EG or for Maintenance Reviews).

7. Agility – Allow EC Members to call for a Maintenance Review Item Exception Ballot up until the end of the Maintenance Review. Current rules require any EC objections to be stated more than 7 days before the end of the review – so the last 7 days of the current review are meaningless and reviews can be functionally as short as 23 days.
Section 4.2.2 added words to move any Item Exception Ballot until after the end of the Maintenance Review. The way it is now if there is a 30 day Maintenance Review, the EC has to raise any objections more than 7 days before the end of the review. So the review time effectively is only 23 days. The easy fix for this is to move the very rare Item Exception Ballots to after the end of the regular review period. This has no impact on JSRs that don't have objections from the EC and allows the complete 30 day review in the by far most common case. This doesn't slow down the vast majority of Maintenance Reviews where formal objections are not raised by an EC Member.

8. Agility - Require that an updated Spec be posted after a Maintenance Review completes successfully.
Section 4.2.2 added words to require posting an updated spec after changes are approved in a
Maintenance Review. There have been JSRs where updated specs are not published after successful Maintenance Reviews. Implementers are expected to read the spec, knowing some of it may be replaced by Maintenance changes and then read each change list in each Maintenance Review and try to figure out what the Spec should actually say. That should not be allowed. If the Spec Lead doesn't know how the Spec changes to the extent that they can update the spec, the change should not be permitted.

9. Agility – Change deadline for requiring special election for EC vacancy to avoid special election occurring too close before the regular election. The current rules call for a special election to fill a vacant EC seat if the vacancy occurs more than 3 months before the next regular election, but given how long it takes to prepare and conduct elections, that could lead to a special election very soon before a regular election, causing confusion. Make that a longer time.
Section A.4.2 changed so no special election if ratified seat is vacated within 6 months of regular
election. With the current 3 months a special election could happen right before the regular election (given the delays in starting and running an election).
Section A.4.3 same change for openly elected EC seat. See immediately above.

10. Transparency – Ensure transparency in Maintenance process by publishing requests for
maintenance changes publicly (e.g on an archived mail list). When a Maintenance Review occurs both these requests for changes and the disposition must be publicly viewable (e.g. deferred with brief comment why, rejected, with brief comment why, included in Maintenance Review).
Section 4.2 Added text requiring a publicly archived Maintenance email feedback address for public comments.
Section 4.2.1 Added text requiring summarizing comments with disposition and making that public along with change log when Maintenance Review starts.

11. Agility - Final Release must be published promptly after Final Ballot Approval. (one JSR was approved nearly 5 years ago and still has not published a final spec.)
Section 3.4. changed to require all materials needed to publish final release are given to the PMO
before the start of the Final Ballot. If they don't have this material, they are not ready for Final Ballot.  Otherwise, what is the EC approving?

12. Agility - Deal with dormant JSRs that are no longer functioning.
Section 2.1.3 changed to say that if group no longer functioning at all EC can vote to replace spec lead (if group not functional enough to vote itself). The new spec lead can either continue or decide to terminate the group.

13. Transparency - Include URL for additional licensing obligations for EG members from 3rd party hosting services (for mail lists, code repositories) in Initial JSR Request. Update with EC if changed.  Some 3rd party services require licensing that is different than JSPA (e.g. host site gets patent grants).
Section 1.2.1 – added text to do the above

14. Elections - Elections voting takes place over a period of 6 weeks from when voting starts to when it completes, making it difficult to focus JCP Member attention on the election process. Change timing of ratified election and open election to improve participation.
Section A.4.3 – rearranged wording to make it a one word change to determine the relative start times of the ratified and open elections. Changed to make ratified and open election voting in same 2 week period. Also requirement to notify on JCP website 4 weeks before start of voting what materials are needed to run in election.

15. Duties of EC - Clarify that duties of the EC in providing guidance to the PMO includes developing and publishing white papers, reports or comments if either one or both of the EC's finds that appropriate.
Section A.3 Duties and Responsibilities item “Provide Guidance to the PMO” - added a couple of sentences. Provide guidance to the PMO <addition>.and JCP Community to promote the
efficient operations of the organization and to guide the evolution of Java platforms and
technologies. Such guidance may be provided by mechanisms such as publishing white
papers, reports, or comments as the EC deems appropriate to express the opinions of one or
both Executive Committees.</addition>.

The program office announced the 2009 JCP Program Star Spec Leads on Friday.

The new Star Spec Leads are Ed Burns, Mike Milikich and David Nuescheler--a big congratulations and sincere thank you to these Stars for their exceptional performance, service and contribution to the commuinty!

The Star Spec Leads Program was launched by the JCP program office four years ago, and recognizes JCP program Spec Leads  who consistently showcase their value through their JSR leadership in their Expert Group (EG) as well as in areas outside their EG, such as establishing best practices, operating transparently and mentoring others.

You can also read about past Star Spec Leads in the JCP Star Spec Lead Hall of Fame .

The January/February edition of the JCP program newsletter is available on jcp.org .

 The March/April edition went out last week and will be available shortly.

The JCP Program Management Office (PMO) presents JCP program awards each year during the JavaOne Conference. This year marks the seventh annual awards, and there is a change in the process to enable more transparency and openness to the community.

This year the JCP program office will accept nominations from the community for the the JCP Program Awards in six categories.  Nominations are open to anyone with an interest in Java technologies and community participation--JCP program membership or affiliation not required! If your nomination wins an award, there is a recognition gift in it for you!  Nominate here.

The categories for the awards are as follows--see the board for a full description of each category (registration for the board posting is very lightweight--only email required):

- JCP Member of the Year
- JCP Participant of the year
- Most Outstanding Spec Lead for Java Standard Edition/Enterprise Edition
- Most Outstanding Spec Lead for Java Micro Edition
- Most Innovative JSR for Java Standard Edition/Enterprise Edition
- Most Innovative JSR for Java Micro Edition

Nominations have been extended and will be open until 1 May 2009.

To find out more about the JCP Program Awards and view previous winners visit this page on jcp.org.

The PMO has been working on a major revision to the jcp.org web site, and we're getting ready to open up the site for beta testing. If you are already a user of the current jcp.org web site, we'd like your assistance in testing the new site to ensure that all the kinks are ironed out before we launch later this year.

 If you are interested in volunteering as a beta tester of the new jcp.org site, send mail with the subject "New jcp.org tester" to pmo at jcp.org before 15 April 2009. Instructions for accessing the test site will be sent to you shortly thereafter.

Deadlines for submitting materials to be posted on jcp.org before JavaOne 2009.[Read More]

The JCP program is currently operating under version 2.6.  I believe the JCP is the only standards organization with a version number?

JSR 215, JCP Program version 2.6, is preparing for Maintenance Review.  Please subscribe to the observer alias for more information.  The JCP Executive Committee is the Expert Group for this JSR.  In the spirit of openness and transparency, the Observer Alias will be used for communications as well as the Community Update Page of the JSR.

Interesting and related thought:

Observer Alias is one of the creations out of JCP 2.6 in March 2004.  You do not need to be a JCP program member to subscribe to any JSR Observer Alias--they are open to the public.  It is at the JSR Spec Lead discretion how to utilize the Observer Alias, but the PMO actively encourages the use of Observer Aliases and other methods of transparenct in the operation of JSRs.  If you are interested in following the activity of a JSR, subscribe to the Observer Alias of that JSR and let the Spec Lead know you would like communications through their Observer Alias.  Let us know your thoughts on Oberver Aliases...

The JCP program office is hosting a panel again this year at QCon London "Open Standards Development: Opportunity or Constraint?".

Panelists include Patrick Curran, Paul Downey, Rod Johnson, Peter Pilgrim and Stephen Colebourne. 

Post your questions you would like addressed in the panel here. 

Lately we have been seeing a surge in JUG memberships. Welcome to the following new JUG members who have joined the JCP program over the past 1-2 months:  JUG-USA, Houston JUG, Connecticut JUG, Oklahoma City JUG, Detroit JUG, Malasia JUG, Polish JUG, Japan JUG, Riviera JUG, Dutchess JUG, Utah JUG, JavaWUG. We also had several Individuals join from around the world: Wei Ming You (Canada), Alan McMichael (USA), Darryl West (USA), Paul Cowen (Australia), Nishanth Vepachedu (USA), Jens Wilkes (Germany), Ali OK (Turkey). And we welcomed one new corporate member: Caucho Technology (USA).  You can view our full member list here.

The program office has extended the deadline for free JCP membership to Java User Groups. In addition to the classic membership benefits,  there is also a special Education discount for Java training classes with Sun Learning Services, assistance getting speakers and logistical support for JUG meetings! 

Only a few more days left to vote in the JCP program Executive Committee (EC) Special Election; there is one seat open on the Java ME EC with a term ending in 2010.  We need the JCP program primary contacts to cast a vote in this election.  There are 4 candidates: 2 corporations--Aplix and Cox Communications, and 2 individuals--Shawn Fitzgerald and Marlon Luz.

Voting is open until 9 March.11:59 PM PDT.  JCP program members--please vote now!  Note: if you do not wish to vote for any candidate, please let us know we reached you, by voting "abstain"; check your email inbox for instructions.

If you are not a member or a primary contact, you can follow and participate in the election Q&A.

Check out the results of the JCP program office survey conducted in late 2008 on the topic of JSR Transparency.

As you might have noticed,  the jcp.org website has been down a few times for a few hours recently.

We have investigating the cause and found that we have been targeted by a bot with a Denial of Service attack that
triggered a bug in the web server that we are currently using ad is causing the server process to crash.

A fix is on its way and will be deployed as soon as possible.

Thanks for your patience in coping with the inconvenience of having the website down in such a critical timeframe as the JavaOne week.

The JCP Program Management Office