Your team should actually view open source as a liability, in the financial sense: You’ve made a commitment (usually implicit) to your community that you’re going to spend money indefinitely to make sure this software gets better and better.
Should You Open Source Your Product? That’s the Wrong Question
Luke Kanies

very nice article. :)

liability. this is a great analogy for opening the code… for how people see it today.

but opening up should always be seen, first, as a blessing: if you create any piece of software that people want to contribute with their time writing code “for free”, how can we look at it in any other way?

of course, it all depends on how we open. there’s no one size fits all, and we can even make the community liable instead.

would you agree?