Monday, January 16, 2006

Chairing the EclipseCon Program Committee

First, I have to warn you that if Bjorn Freeman-Benson ever approaches you and says, "Hey, wanna chair EclipseCon? It really won't be much work..." you should turn and run. Fast.

Seriously, it has been a lot of work, but also very rewarding. Bringing a program together is challenging in many ways - at its heart, it's a fundamentally large bit of secretarial work, because there are many submissions, different categories, possible tradeoffs (more short talks and fewer long talks?), and a myriad of small issues (such as not putting two talks with the same likely demographic at the same time).

The program committee also has to look at the balance of the program, which is challenging in other ways - you don't want all the speakers to come from one company, or just from a few projects, or to just represent developers. We looked at different constituencies (committers, users, member companies, IT decision makers, etc.) and tried to ensure that some portion of the conference program would appeal to each of them. We also looked at a balance of old, current, and new technologies, because not everyone has been to conference before or is new this year. Finally, we tried to ensure that a few "virtual tracks", this year focused on RCP and embedded tooling, provided a credible draw for conference goers interested in those topics.

Apart from the sheer difficulty of reading and discussing so many submissions (and it's still going on - we're currently working on the short talks), one aspect of the program committee that proved challenging was trying to increase community involvement. This year we experimented with using a Bugzilla-like approach to submissions, which included allowing anyone to comment and even to vote on their favorite talks, including asking questions of the submitters. Ideally we would like to continue empowering the community, including the ability to rate comments by others and search more easily by adding additional submitter (and maybe community-provided) metadata in the submission form.

I'm looking forward to EclipseCon (ok, in part because my job as program chair will be over ;-) and hope to see you there - I'll be on an open source contributions panel discussion, the final plenary session, doing opening remarks one morning, and participating in the WTP events. If the abstracts are any indication, there will be plenty to learn about!

Onward and upward - M4 released!

Three interesting bits of news to report.

First, WTP's first step toward the 1.5 release and the Callisto train has occured. Go to the M4 down page for a version of WTP similar to 1.0 (with a few extra bug fixes thrown in; technically this is also a 1.0.1 I-build) but that works with M4 of Eclipse 3.2 and the other WTP prereqs.

Second, we've fixed some perf issues reported against 1.0, some of which represented regressions late in the release cycle. If you've experienced these and are feeling the pain, also check out the link above for fixes. (And if you still have perf issues, please report them - performance is a key deliverable for the 1.0.1 service pack.)

Finally, it's official: the Dali project, a technology project representing the merger of the former JSR 220 and EJB 3.0 technology projets, is here. This is great news for the Eclipse community and WTP in particular, because it means some of the strongest supporters of these technologies (Oracle, Versant, Sybase, Solarmetric, JBoss, and others) are all working together in a coordinated fashion on a single technology project. When these technologies mature, they will graduate into WTP and DTP as appropriate. See the Dali site for more details.