In the past, our focus has been on trying to convert non-contributors into contributors, or at least to understand the process of contributing code to Eclipse, but I wonder if we could focus on something a little different this time. Just an idea...choose a date where we have people pair up (virtually) for a few hours to work on an IDE-related bug that crosses boundaries and so we can tackle, or at least start to get a handle on these IDE bugs that have not been addressed before.
The biggest issue IMO is how do we choose what to work on?  Must be useful, but not so complex that it would take too long to solve.
We also need to find a general time that people can collaborate.  For things like this, collaborating in person is best, but since we are all so distributed, I don't see this happening too much.
Also, I don't see this replacing other Eclipse hackathons, since this one would focus more on committers collaborating to fix IDE bugs, rather than on mentoring new contributors.  Thoughts?