By dannycoward on Oct 19, 2007
Any of you who have been involved with any of the Java Platforms for the last 9 years may well have been involved in a Java Specification Request (JSR) or two at some point since that's how we develop APIs for the Java platforms. And any of you who have been involved in a JSR will have noticed that the JCP has an executive body of members of the JCP, called the Executive Committee, who take a vote at various stages of the development of the JSR on how its progressing.
Although the prospect of losing a vote at one of the key stages can be a worrying one, happily most of the time JSRs are in good shape and make it though. For a standards body, the JCP gets things done fairly quickly (oxymoron or miracle ? ), with about an 18 month gestation period for new JSRs, from conception to birth. It still surprises me, therefore, that in what some consider to be a high-speed dash to standardize an API (others a crawl), that there aren't more casualties of the Executive Committee reviews.
The JCP Executive Committee reforms itself on a yearly basis, with some of the seats coming up for grabs each year. One of the interesting parts of this process is the period of open election, where any JCP member can put their name forward for the ballot to be elected to the EC. That's the period we're in right now, so if you're one of the many members of the JCP, you can throw your hat in the ring.