Friday, June 23, 2006

Callisto: name, effects and other such things

Mike recently blogged about Callisto culture, and I'd like to add some observations from DTP. As he said, no project was forced to join Callisto and, to be honest, when the first offer came to DTP, I paused, for many of the same reasons Mike describes. But DTP signed up as well, and we're glad to have done so. Being a relatively new project, Callisto offered us a chance to learn about delivering software successfully at As you might imagine, just getting the code in place (with all that entails) is only one part of the puzzle. Working with the entire Callisto team, especially going through the endgame together, was a great learning experience. While everyone involved did a lot of work, Kevin Haaland (of platform fame) provided invaluable experience, and David Williams (WTP) was relentless in execution while managing the update process, despite the fact I clearly remember that he was not present when volunteered to do that job. :-)

And then there's the name "Callisto." Alex recently made some interesting observations about naming at I'll now confess: I liked the original name "Eclipse release train," since I imagined being able to use a particular Ozzie song in my presentations when talking about it... Well, maybe later.

As Alex says, words tend to end up meaning something other than the original intention. I think in some cases this happens because people take the word to mean what they hope for. And I think this is the case in the semantic shift of "get 10 projects to build at the same time" to "get 10 projects' code integrated, remove duplication, consistent UI, etc. etc." The question then becomes: if (certain segments of) the community want the second type of integration, who will deliver it? My answer: the community should! (DTP committers are one part of this community, of course.) I often have conversation like this:

Someone: I'd like to work on DTP....
Me: Cool, what are you interested in? We have lot's of areas.....
Someone: But, you know, I don't have a lot of time to devote to it so, maybe later.

Speaking at least for DTP (and so it seems, based on studies, most other oss projects), being a committer isn't as time consuming as you might think. Sure, there is a core team that spends a lot of time on DTP each day, but there are also a lot of people who contribute occasionally. All of these contributions are valuable, and all of them are appreciated!


Blogger zx said...

On the note of getting people to contribute/commit... I've been thinking of adding a new keyword to bugzilla to show what bugs are low hanging fruit and easy for people to submit patches too... so they can become contributors... I believe Eclipse has a high barrier to entry for contributors because I think people think it's really hard to contribute when it's not... I want to change this (

Also, Crazy Train is my karaoke song ;)

4:40 PM

Blogger Christian said...

zx, that's a great idea. Eclipse definetely is kind of complex, which results in a pretty high barrier, as you said. But starting to work on some easy bugs could help Eclipse in two ways:
1) Well, they would hopefully get fixed :-)
2) The contributor would learn about Eclipse, possibly enabling him to work on something more difficult next time.

4:57 AM

Blogger John Graham said...


Excellent idea, and I just voted for the bug.

-- John

3:17 PM


Post a Comment

<< Home