The 2017 Fall Executive Committee (EC) Elections process is now complete. The EC Elections process was launched in June 2000. This election was hosted by Votenet and closed on 13 November 2017 at 11:59 PM Pacific Standard Time.

This year, there were 8 Ratified, 3 Elected and 1 Associate Seats open for election.


Congratulations to the following JCP Members as the elected EC Members.

Ratified Seats (all serving a two-year term): ARM, Credit Suisse, Fujitsu, Hewlett Packard Enterprise, IBM, Intel, Red Hat and Sociedade de Usários da Tecnologia Java - SouJava

Elected Seats (all serving a two-year term): Twitter, Hazelcast and Tomitribe

Associate Seat (serving a two-year term): Andres Almiray (it was a tie; see the EC Election Tiebreaker Process section for more details)

Newly elected EC Members take their seats on Tuesday, 28 November 2017.

Voting Period: 31 October - 13 November 2017

Number of Eligible Voters: 1177
Percent of Eligible Voters Casting Votes: 32.97%

Number of Full and Partner Members Eligible to Vote: 768
Percent of Full and Partner Members Casting Votes: 23.70%

Number of Associate Members Eligible to Vote: 409
Percent of Associate Members Casting Votes: 50.37%


Ratified Seats:

Elected Seats:

The top three (3) candidates have been elected.

Associate Seat:

The top one (1) candidate has been elected using the defined Tiebreaker Process - see the EC Election Tiebreaker Process section for more details.

For more information about the candidates who ran for the 2017 Executive Committee Election, please visit the 2017 Executive Committee Elections Nominees page.

All votes for the 2017 JCP Executive Committee Elections were tallied by Votenet, and the results of the Associate Seat voting were a tie. Determining the winner required using the tiebreaker procedure originally defined on October 18, 2011.

Per section 3.7.6 of the JCP document version 2.10, we used the RFC2777 Gateway Form at https://www.w3.org/2001/05/rfc2777 to determine the winner. In order for the numbers to be random, we took the following steps:

1) On Thursday, 16 November 2017, at 10 AM PST, the PMO would assign a number (1 or 2) to each of the two candidates based on the closing value of the NASDAQ Composite Index as shown on http://quotes.wsj.com/index/NASDAQ/historical-prices for Wednesday 15 November 2017. If the closing value's whole number (ignoring any fractional part of the number) were even, the PMO would assign the 1 and 2 to the candidates alphabetically by last name. If the closing value's whole number were odd, the PMO would assign the 1 and 2 to the candidates in reverse alphabetical order by last name.

2) On Friday, 17 November 2017, at 10 AM PST, the PMO would use the RFC 2777 form. First, the PMO would enter "2" into the "Size of pool" field. Then the PMO would enter whole number values into the three "Random Number" fields in the RFC2777 form, noted at the same time and as described below:

a) For "Random Number #1": the closing value of the S&P 500 Index (ignoring any fractional part of the number) as shown on http://quotes.wsj.com/index/SPX/historical-prices for 16 November 2017
b) For "Random Number #2": the closing value of Dow Jones Industrial Average (ignoring any fractional part of the number) as shown on http://quotes/wsj.com/index/DJIA/historical-prices for 16 November 2017 (*)
c) For "Random Number #3": the final, winning score of the Golden State Warriors-Boston Celtics basketball game played on 16 November 2017 as shown on http://www.nba.com/scores#/

* - The PMO decided on Wednesday 15 November 2017 to use the Dow Jones Industrial Average as a different number of greater variance than what was originally described. The PMO had intended to use the peak temperature in San Jose, California but made the change after realizing that San Jose's predicted vs reported peak temperature for Thursday didn't have sufficient variance.

The closing value whole number of the NASDAQ Composite Index for 15 November 2017 was 6706, an even number. The PMO assigned 1 and 2 to the candidates alphabetically by last name, per step one of the predefined JCP EC Election Tiebreaker Process described on Tuesday 14 November 2017. Thus, candidate Andres Almiray had been assigned number 1, and candidate Werner Keil had been assigned number 2. On Friday 17 November 2017, these assigned numbers would be used to determine who would be elected to the Associate Seat, as described in step two of the JCP EC Election Tiebreaker Process.

The result of the 2017 EC Elections tiebreaker for the Associate Seat is:
Andres Almiray has been elected to the Associate Seat.

The result was determined as per the procedure specified in section 3.7.6 of the JCP 2.10 document, using the two-step Tiebreaker Process described on 14 November 2017.

The step one results were determined Thursday 16 November 2017, with Andres Almiray assigned number 1 and Werner Keil assigned number 2.

The step two results were determined Friday 17 November 2017, with the PMO entering the numbers taken from 16 November 2017 into the form at https://www.w3.org/2001/05/rfc2777, as follows:

Size of pool: 2
Random number #1: 2585 (closing value of the S&P 500 Index, ignoring any fractional part of the number)
Random number #2: 23458 (closing value of Dow Jones Industrial Average, ignoring any fractional part of the number)
Random number #3: 92 (final, winning score of the Golden State Warriors-Boston Celtics basketball game)

Using those numbers, the form returned the number 1 which corresponded to the number assigned to Andres Almiray.
Therefore Andres Almiray has been elected to the Associate Seat.

The 2017 Fall Executive Committee Election final results have been announced on Friday, 17 November 2017.

ABOUT THE JAVA COMMUNITY PROCESS (JCP) EXECUTIVE COMMITTEES

Under the JCP 2.10 rules, there are 16 Ratified Seats, 6 Elected Seats, 2 Associate Seats and the permanent seat held by Oracle America. Members serve 2-year terms that are staggered so that 12 of the 24 seats are normally up for ratification/election each year.

The EC members guide the evolution of the Java technologies. The EC represents a cross-section of both major stakeholders and other members of the Java Community. Duties are: select JSRs for development, approve draft Specifications for Public Review, approve Final Specifications, review TCK appeals, approve Maintenance revisions and possibly defer some features to a new JSR, approve transfer of maintenance duties between members and provide guidance to the Program Management Office (PMO). For more information on the EC, see the Executive Committee Info page.

2017 Special EC Elections Results

2016 EC Elections Results

2015 EC Elections Results

2014 EC Elections Results

2013 EC Elections Results

2012 EC Elections Results

2011 EC Elections Results

2010 EC Elections Results

2009 EC Elections Results

2008 EC Elections Results

2007 EC Elections Results

2006 EC Elections Results

2005 EC Elections Results

2004 EC Elections Results

2003 EC Elections Results

2002 EC Elections Results

2001 EC Elections Results

2000 EC Elections Results


For more information on the JCP, see the JCP Overview page.

Contact the PMO for election questions at pmo@jcp.org.