JCP Program Office blog covers news from the Java Community Process program office

  • October 17, 2012

2012 EC Election Ballot open; Meet the Candidates Call tomorrow

Guest Author

The JCP Executive Committee (EC) Election ballot is now open and all of the candidates' nominations materials are now available on JCP.org -- note that two new candidates were nominated late last week:  Liferay and North Sixty-One. It is shaping up to be an exciting election this year!

The ratified candidates are:  Cinterion, Credit Suisse, Fujitsu and HP.
elected candidates are (9 candidates, 2 open seats):  Cisco Systems, CloudBees, Giuseppe Dell'Abate,
Liferay, London Java Community, MoroccoJUG, North Sixty-One, Software AG, and Zero Turnaround.

Tomorrow, 18 October, we will hold an open teleconference for the
Java Community to meet the candidates and ask questions regarding their
nomination.  We hope you will be able to participate in the call. 
Should the time be inconvenient, a recording will be made available for
download, and candidate questions may be posted on this blog entry or
sent to pmo@jcp.org.

Topic: Meet the EC Candidates
Date: Thursday, October 18, 2012
Time: 9:30 am, Pacific Daylight Time (San Francisco, GMT-07:00)
Meeting Number: 807 818 225
Meeting Password: MeetEC

To join the online meeting (Now from mobile devices)
1. Go to https://jcp.webex.com/jcp/j.php?ED=186721592&UID=0&PW=NMmUzNjY5ZTMw&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: MeetEC
4. Click "Join".

To view in other time zones or languages, please click the link:

To join the audio conference only

    +1 (866) 682-4770
    Outside the US: global access numbers  
or +1 (408) 774-4073
    Conference code: 9454597
    Security code: JCPEC (52732)

For assistance
1. Go to https://jcp.webex.com/jcp/mc
2. On the left navigation bar, click "Support".

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.