Follow my microblog on Twitter at dougschaefer

Monday, May 25, 2009

Building Communities

There's been a couple of times now that presentations I've made have been recorded for posterity. I don't usually listen to them, mainly because I'm worried it really sucked and I felt embarrassed. But the main stage presentation I gave at EclipseCon was different on many levels. And having just finished listening to it, I'm glad it's been captured. It's available at Eclipse Live here:

http://live.eclipse.org/node/739

The title of the presentation is "The Rise and Fall and Rise of the CDT: Lessons on Building Communities". It is a very personal look at the history of the CDT and the lessons I learned about building communities through the roller-coaster ride I've been on for the last 7 years working on the CDT.

This little presentation is my proudest moment of my career. I put a lot on the line with it and you can tell at the beginning I was a bit nervous about that. But listening to it today, I am very happy with how it went.

If you are curious about my philosophies on working in open source communities, or just curious why I'm such a crazy man, here's an open window into my soul. And there is some humour to keep things from getting too serious.

3 comments:

rchaves said...

I just heard it and it was a pretty good presentation, great to hear your view on working in the CDT project, Doug. Being an ex-committer for Platform Core, I could relate to some of the things you mentioned, but at the same time learned about the many ways life in CDT is different.

One thing you said didn't sound right: that a company could make changes and improvements to CDT and not have to contribute their changes back. That sounds to me like a violation of the EPL. Unless:

a) they are not redistributing, or
b) they made improvements by extending CDT with non-EPL classes, without having to make changes to the CDT code.

Or did I misunderstand you?

Doug Schaefer said...

I think that's a misconception people have. The license states that you have to be able to provide the source code to your licensees, i.e. downstream. It doesn't say anything about upstream. This is even true for GPL.

Now if customers of these vendors would get the source, they can contribute the changes. But that doesn't happen from my experience.

Rafael Chaves said...

You are right. Sounds minor but if their user base is small it can really mean nobody will ever see that code...

I bet they didn't ship an evaluation version... :)

Post a Comment