Let the Voting Begin!
Voting begins today for the 2011 Eclipse Foundation Board of Director elections. We have a great slate of candidates, each of whom brings a great deal of knowledge and experience with the Eclipse community to the table. I highly encourage everyone to get involved with this process and vote! I cannot overstate how important these elected directors are to the functioning of the Board, the Foundation and the community.
If you are eligible to vote, you should soon be receiving an email with your voting credentials. If you believe you are eligible, but do not receive credentials, please contact webmaster@eclipse.org.
Eclipse Foundation Elections
Just in case you hadn’t noticed, the nominations are in, and the “campaign” phase of our 2011 Board of Director elections in now in full swing.
I have to say that I am particularly impressed with the quality of the candidates this year. There are a lot of well-known and well-respected community leaders who have thrown their hats into the ring. Every one of them should be commended for volunteering their time and energy to improving the Eclipse community and its governance.
The Eclipse Foundation has a unique governance model in the open source world, and one which I believe works extremely well. As I recently commented on the OpenJDK governance conversation:
The Eclipse Board explicitly has a mix of business-centric and community-centric representatives on it. In practice, it has actually worked well because the diversity of views have generally speaking resulted in better decisions. Diversity takes many forms, but it is almost always a force for good.
The people running in this election are your community-centric representatives. They have an enormously positive influence on the Board’s decisions, and the elected directors past and present have been a big part of our collective success.
I strongly encourage everyone within the Eclipse community to check out the candidates pages, ask questions on the foundation forum and vote in the coming weeks!
OpenJDK Governance
On Friday, Mark Reinhold, mentioned that I have recently spent some time helping to help flesh out a draft governance model for the OpenJDK community. As John Duimovich described it, our goal is for OpenJDK to be “…an open, transparent, and meritocratic project that can be run in a lightweight and efficient manner”. I think we’ve largely succeeded in getting there. But it is important to recognize that when the document is (soon!) made public that it is a draft. I expect that many people will have comments and feedback, and I look forward to hearing them.
I do not have a prior history of involvement with the OpenJDK community, so being asked to contribute to this process was both an honour and a pleasant surprise. But given that Eclipse is also a community which involves participants ranging from individuals to some of the world’s largest corporations I believe we have some experiences which are helpful and relevant to the governance of OpenJDK. I hope that I’ve made some useful contributions which help the OpenJDK community off to a great (re)start.
Introducing Orion
Sometime later today some very exciting new code is going to show up in the e4 git repository at Eclipse. “Orion” is a brand new adventure for Eclipse, and one which we hope will interest and excite a whole new community: web developers.
Orion is not a set of Java plug-ins which run in the existing Java IDE. It is browser-based open tool integration platform which is entirely focused on developing for the web, in the web. Tools are written in JavaScript and run in the browser. Unlike other attempts at creating browser-based development tools, this is not an IDE running in a single tab. Links work and can be shared. You can open a file in a new tab. Great care has been taken to provide a web experience for development.
Orion’s server-side is currently a simple OSGi-based Java application using Jetty as its web container. But the communication with the client is through a fairly simply RESTful interface, and we definitely hope to see implementations in other languages and technologies.
I cannot emphasize strongly enough that this is not the same old same old from Eclipse. Orion is a new code base, whose client-side is written in JavaScript and provides the foundation for a new and different web tooling platform. We hope that a new ecosystem of web tools will emerge that make it easy to link together a web developer’s toolset.
Another key point is that Orion is not finished. It is not, for example, a complete JavaScript IDE. This is the very beginning of a new project, and everyone involved knows that we have a lot to learn. Unlike the early days of the Eclipse project itself, the team from IBM is contributing a relatively modest — but very useful — piece of code to spur the creation of whole new community of contribution and participation. We invite everyone who is interested to try the code, join the mailing lists and forums, and figure out ways to both adopt and contribute to the work that has been done. Even more importantly, we are looking for people and organizations to get engaged in Orion in meaningful leadership roles for everything from adding code to defining the project to prioritizing the roadmap. We know that this needs to be a community-led process.
The team is going to be blogging about the details of the technology, so I won’t steal their thunder. But hopefully the screen shots will spur your interest. Certainly we think there is a very interesting and highly scalable editor tool which a lot of web developers are going to be interested in both using for their code and embedding in their applications. Update – you can now download the Orion code.
So today is the very beginning of something new. But there is a lot of work to do, and first and foremost we need you the community to provide feedback and to get involved. For those who can make it, we are going to have a face-to-face meeting in Ottawa the first week of March to discuss where we can collectively take Orion. The output of this meeting will be a first draft of a project proposal for the community to review.
So to set expectations, here are a few key dates to keep in mind.
- This week we are going to get the initial code contribution into Eclipse’s git repository and some initial documentation into the wiki.
- Next week we are going to start inviting a small number of people to try out the technology hosted on our servers.
- By the end of January we will have a much broader trial available on our servers, and we will be inviting the entire Eclipse committer population to try it out.
We are awfully excited about the potential of the work done to date. Stay tuned!
Update: Changed the screen shots to show the Orion wordmark, rather than Eclipse.
Update: Added links to the wiki pages and Boris Bokowski’s blog post.
Christmas Comes Early for Java Developers
Today Google announced that they will be contributing two key pieces of Java tooling technology to proposed Eclipse Foundation projects. Two new projects are bringing to Eclipse product-quality code which have been highly regarded by Java developers for many years. They will fill major requirements that the Eclipse developer community have been hoping to see in open source for a long time. The WindowBuilder project will be led by Eric Clayberg of Google and Pavel Petrochenko of OnPositive Technologies will lead the Runtime Analysis Tools (RAT) project.
WindowBuilder is one of the best Java GUI builders out there. It supports both SWT and Swing and is fully bi-directional, meaning that you can work on the code or the visual design – it’s your choice. Just as importantly, the architecture is extensible so the team hopes to see additional designers built on top. Part of the goal here will be to hopefully create an ecosystem of open source and commercial extensions that make use of WindowBuilder’s core functionality to create GUI designers, as Google plans to do with its GWT Designer offering. [Update] Google already has a great start at creating community around this project by welcoming committers and contributions from Genuitec (Swing and mobile tools), compeople(Riena support) and Cloudsmith (data binding support).
CodePro Profiler is an excellent Java application profiling tool, and forms the basis for the code contribution to RAT. The profiler supports Java developers to inspect the running applications, find performance bottlenecks, detect memory leaks and solve problems regarding thread concurrency in your Java applications. Great Java application profiling is something that Eclipse users have wanted for years, and soon it will be here.
Both projects intend to join the Indigo release train in June 2011. It will be a lot of work for the teams, but having these projects available so quickly will be great for Java developers who use Eclipse. I know that the teams are very interested in growing community participation, so if you can help please join in on the conversation on the Proposals forum.
Google has been a big supporter of Eclipse for years. They are a long-time Solutions Member of the Eclipse Foundation, last year they provided an additional $20,000 to us to improve the server infrastructure for our projects, they provide the hosting for Eclipse Labs, they support us in the Google Summer of Code and they run the Eclipse Day at the Googleplex each year. But this is the first major code contribution to the Eclipse community from Google. I hope you will join me in thanking Google for making this happen!

