As I explained in this blog last year, we use the Process
to change the Process. The first of three planned JSRs to modify the way
the JCP operates (JSR
348: Towards a new version of the Java Community Process) completed in October
2011. That JSR focused on changes to make our process more transparent and to
enable broader participation.
The second JSR was inspired by our conviction that Java
is One Platform and by our expectation that Java ME and Java SE will become
more aligned over time. In anticipation of this change JSR
355: JCP Executive Committee Merge will merge the two Executive
Committees into one.
The JSR is going very well. We
have reached consensus within the Executive Committees, which serve as the Expert
Group for process-change JSRs. How we intend to make the transition to a single
EC is explained in the revised versions of the Process and EC Standing
Rules documents that are currently posted
for Early Draft Review. Our intention is to reduce the total number
of EC seats but to keep the same ratio (2:1) of ratified and elected
seats.
Briefly, the plan will be implemented in two stages. The October 2012 elections
will be held as usual, but candidates will be informed that they will serve
only a one-year term if elected. The two ECs will be merged immediately after
this election; at the same time, Oracle's second permanent seat and one of IBM's
two ratified seats will be eliminated. The initial merged EC will therefore
have 30 members.
In the October 2013 elections we will eliminate three more ratified seats and
two elected seats, thereby reducing the size of the combined EC to 25 members
(16 ratified seats, 8 elected seats, plus Oracle's permanent seat.) All remaining
seats, including those of members who were elected in 2012, will be up for re-election
in 2013; that election should be particularly interesting. Starting in 2013
we will change from a three-year to a two-year election cycle (half of all EC
members will be up for re-election each year.)
We believe that these changes will streamline our operations, and position
us for a future in which the distinctions between desktop and mobile
devices become increasingly blurred.
Please take this opportunity to review and comment on our proposed changes
- we appreciate your input.
Thank you, and onward to JCP.next.3!
