It’s that time of year again…EclipseCon North America submission time.
Like every year, the program committee is asking you to submit your talk early. Ian and Doug have been cracking the whip pretty hard telling us to blog, so here I am. One of the topics that came up recently is how do we choose the talks, what are we looking for, who are the rock stars that people want to see. One sure way is to ask what you want to see or attend at the conference, so provide your feed back here, to Doug, Ian, or any of the other committee members.
Last year, I referenced a paper, “How to Get a Paper Accepted at OOPSLA“, in which it outlined some of the items that, that committee was looking for in a submission. So I’ll jot down some things that I’m looking for below.
I don’t have a particular technology or niche that I focus on any more, it used to be XML and the related technologies around it, but in most cases the XML tools at eclipse are good enough for most people’s uses. So I’m not necessarily looking in that area, unless something REALLY REALLY cool comes along. Also if you submitted the same talk in the past or presented it in the past….not interested.
I’m more focused over the last year or two on quality of the code that is produced by a project and developers in general. How to make sure we keep the code maintainable and the practices around that. So static analysis tools like PMD, and FindBugs are interesting, but I want to know how your projects are using these tools to improve your code. What are the new and interesting things coming out of these tools? Projects like Code Recommenders peak my interest, and the additions they provide. Mylyn…well they do interesting things, so I’m looking not so much the Core Mylyn task oriented project, but their sub projects, and how they are improving developers lives.
Experience reports from projects migrating to or from a centralized version control system to a distributed version control system. The pains, the gotchas. How can EGit be improved, how are you using JGit to get your work done. Has moving to a distributed version control system made your life easier, harder? Are they over hyped?
Builds…Builds…Builds. The battle of the builds continues to happen, but more importantly what can we do about p2? p2 started as provisioning system for an application, but is being used more and more for to provision a build and a repository for those build artifacts. Are you doing any work in the enterprise or open source projects around addressing the issue of stale or non-existant p2 repositories. How does this affect the reproducability of your build? Are there ways to address this? How does the p2 model of a repository compare the Maven Central concept? Should the Eclipse foundation replicate the model for p2 and if so how?
What are the problems that a project and committers coming from a corporate environment experience when working on a previously closed project that is now open? How did you adapt, what leasons can be taken away from this?
The web and mobile space is still hot, but how do we evolve our development environment and particularly the eclipse interface to the new touch screen mentality? Is there something within Eclipse 4.x platform that allows for adapting to the new platform? Is SWT even the right technology going forward? Should we be looking at new ways to develop our user interfaces so they are cleaner and easier to use? How do we get more UI specialists involved with open source projects in general?
In general, I’m interested in things that challenge the status quo, that make me think, and challenge my beliefs. That help make me more productive, improve the quality of the code I produce, and make it easier for people that use that code. Give me more demos, and less talk. For tutorials, I really want lots of hands on, and short introductions to the topics that will be worked on in an exercise. Get me up and running quickly.
I look forward to your many submissions.