A funny thing happened on the way to EclipseCon (another e4 post)
Although it’s normal to be judged based on actions, sometimes if you know the person’s intentions it can help you change the way you feel about it.
So with regards to this whole e4 debacle, let me say that our intentions really were honourable!
We on the platform team care passionately about Eclipse. We know you do too. We want to see it live a long, healthy life. We want it to serve its community as best it can. When we can’t achieve that it makes us sad. It’s clear to us that for Eclipse as a platform to remain long lived, vibrant, and relevant, it must be able to change. But the weight of a zillion plug-ins, projects, and API means the path of least resistance is stagnation, and the effort to effect change given the current constraint system is becoming monumental.
Therefore, two things must happen:
- A new space must be carved out in which experimentation can happen, leading to change.
- New people must get involved, bringing with them their energy, ideas, requirements, knowledge, passion.
These two are intrinsically tied.
That is e4.
We have some ideas. We want to share those ideas. Of course the #1 place to share them is EclipseCon, amongst the community that cares. This discussion is important. Last year’s discussion was vague because of course there were just glimmers of ideas, leaving smart people like Chris puzzled. We needed to be more concrete in expressing these ideas.
We need some demos!
Why? Because for one, talk is cheap, but code speaks volumes. Second, because we all love code, working code, code that does something cool. That’s why we do what we do for a living. And finally, because code is the prose of our ideas.
So we’ve been working very very hard to put together a few demos that hopefully would feel compelling to people, would get them excited. Would make them go, “hey I gotta get involved in that, where do I sign up?!”. And of course would express our ideas.
Now as Bjorn pointed out, given that our goal is A New Era of Openness (tm), then working on these demos outside of the community spaces isn’t a good start. That’s true I suppose, but please consider it from a different angle:
Have you ever worked on an email that was super super important? Of course you have. You want to make sure that as much as possible it matches what you have in your mind. But your thoughts are unclear. So you write a draft. You don’t send it right away. Instead, you edit it again and again. Maybe you have a close friend have a look at it to give feedback. You do all this because the act of writing the letter helps clarify your thoughts. And because you know you’ll only get one shot to make a good first impression.
That’s what we did (well, not the first impression part obviously, sigh).
Then someone said, “Well gee these guys are going to want to run the demos themselves, see the code.” Rightly so! We need a place to put it…
And then someone else said, “You know if this takes off then we’d like to avoid moving the stuff because we’ll lose history etc. We should create it in such a way that would avoid that.”.
And that’s when the trouble began. Because you can’t just simply make such a little place in Eclipse, on the side, to show people something. You need to start this big engine up that eats web forms and emails and burps out that place. And that engine is a public engine…
Others have explained what ensued. You know, we’re not marketing people. We’re just developers in a hurry hacking some code for others to see, trying to make this process stuff go away so we can get back to that. Naive, yes. But well intended.
On a positive note, we’ve already (and in advance too!) achieved one of our goals, which was to get people talking about e4!! Hrmmmm…
More seriously, if Eclipse is to move forward, then it needs to shed some of its baggage, like obtuse programming models, overgrown APIs, etc. And we too equally, if not more so, need to shed our own emotional baggage. Otherwise we’re stuck with the same models (programming and mental) that will only result in the same past being retread. No future in that.

March 7th, 2008 at 8:49 pm
Kevin, I’m shocked you don’t blog more often. I suspect you’ve been practicing somewhere in some secret location; there wouldn’t happen to be some incubator project with prior drafts would there? That would be just like you closed platform types! Oops, did I say that? I didn’t mean that at all! Someone put words in my mouth. I think it was those people from Wind River who made me say that. I would never say something like that normally. I’m way too diplomatic! Really!!
I love reading the Eclipse blogs, and I especially love to get an insight into how people think. Of course I love the technology, but I’m particularly fascinated by the psychology that drives people and their underlying machinations. I read between the lines when I have to. Please let the community know your thoughts more often.
March 8th, 2008 at 10:42 am
Thanks Ed. Actually you found me out, I have a whole year’s worth of blogs all in draft, secretly squirreled away ready to be released. I’m thinking of calling it, “k4″…
Yeah I too am fascinated by the psychology. (Not to make this a mutual admiration society but) I really enjoy your blogs for those kinds of insights and it reminds me that there is space for that. All this has in fact taught me that I and others on the platform team should blog more often. You know, its not that we’re trying to be secretive, its just that many of us work in the same hallway and its easier to just shout things out to each other. But I love the healthy conflict of different viewpoints, and I can usually now guess what people here are going to say to anything, so more open communication would be a relief through variety ;->
March 8th, 2008 at 5:49 pm
“Have you ever worked on an email that was super super important?”
If you had written, “have you ever worked on an open email that was super super important”, then I think the analogy would have worked. But, in fact, emails are not open - they are closed - once sent, they are not modifiable by a community. An open email would be a wiki page and those *are* worked on in public.
“Maybe you have a close friend have a look at it to give feedback.”
I think the feedback you all are getting is that the set of all Eclipse committers (across the major projects) consider themselves the Platform’s ‘close friends’, but apparently that relationship is not reciprocated.
Now, I strongly believe that you and McQ and Steve and everyone wants to have that two-way relationship and I strongly believe that this brou-ha-ha is an error in outgoing communication rather anything evil, but the bad feelings are out there and so extra care needs to be taken to be more open than even you think is necessary… Anyway, that’s just my opinion.
March 10th, 2008 at 2:40 pm
Hmmm, I’m guessing Bjorn that you don’t write your draft emails to the community in a wiki.
March 11th, 2008 at 10:50 am
I do draft important documents in public - documents that involve lots of controversy and community, e.g, http://www.eclipse.org/projects/dev_process/development_process.php, http://eclipse-projects.blogspot.com/2006/11/edp-summary-17-of-17.html, http://wiki.eclipse.org/index.php/Ganymede_Simultaneous_Release (the must dos section), etc.