Powered By:
Clearspace
BlatherSource: Because development won't keep quiet
Currently Being Moderated
3

When Worlds Collide

Posted by Daniel Henninger on Apr 2, 2007 8:46:07 PM

You know, when you are working by yourself on an open source project, your schedule is your own.  If you decide you don't want to work on it for a couple of months, that's your perogative.  At some level there's no rules what-so-ever aside from not doing things that will drive folk away from being interested in your project (assuming you care).  One of the biggest things that drives the project, however, is what -you- want.  When you are working on an open source project where you are teamed up with others, there's some checks and balances over what you do and your partners do.  However, at the end of the day, it's the same type of situation, you all decide what the focus of the project will be.  I don't like to put it like this, but no one has a "right" to your time except for you.

 

When you start working with a company on an open source projects, things change.  There are deadlines that the company is pushing for help drive your own timeline.  There are things they'd like to see happen that you may or may not agree with.  Instead of saying "well unless you submit a patch, it's not happening", you tend to work something out instead.  It's an interesting adjustment to "normal open source projects".

 

Do I dislike either?  No.  In fact I've quite enjoyed the experience of it.  It's taught me a few things that I wasn't aware of.  Like I was rather blind to some of the requirements that corporations ask for.  Some of the things they ask for I would typically have thought "that's ridiculous" with some of my other projects, but here I see a lot of folk bringing the same issue up and I start to discover that the issue is more commonplace than I would have assumed.  I'm not citing any examples here.  Just suffice to say there's things that having a broader knowledge of the corporate world has made me reconsider some of the decisions I might have made with other projects in the past.

 

So many thanks to Jive Software for giving me this additional experience that I wouldn't have gotten probably with PyAIMt and PyICQt.  =)  It's been fun and I hope it continues to be fun!



Add a comment Leave a comment on this blog post.
Apr 2, 2007 10:16 PM Guest Matt Tucker  says:

Definitely an interesting topic. It's a challenge for us as well. Open Source development to put food on the table is different than dev to scrath an itch. I'm pretty happy with how we've all managed things so far -- lots of good stuff to learn on both sides.

 

Apr 2, 2007 11:13 PM Guest Daniel Henninger  says:

Indeed, I am happy how it's all worked together too!  I often feel like it must suck for you all to not be able to really ... well you know, "require me" to have something done by a certain time.  But I believe we all communicate well and are able to set realistic goals amongst ourselves.  As you recall, I was tenative about getting involved at first, but I have not regretted a bit working with you all.  =)

 

May 10, 2007 9:23 AM Guest David  says:

"reconsider some of the decisions I might have made with other projects in the past."

 

Hay,

 

Can you share what these kind of decisions would be? So that I don't make the same mistakes maybe

 

Cheers,

 

David