Someone whose opinion I respect asked me today whether we've ever considered releasing BlueDragon as open source. He was trying to make the case that we could make more money that way. Frankly, I'm not convinced. I certainly see how it could make BlueDragon more popular--but make more money? I'm not so sure.
But it is interesting to think about. So here are my questions:
- Would you be interested in an open source version of BlueDragon? Why?
- If BlueDragon was released as open source, would it make it less appealing to you? Why?
- Which editions would you want to see as open source? Java/J2EE? .NET? both? neither?
- Would you plan on using an open source version of BlueDragon in production? or only for development and testing?
- Would you use an open source version of BlueDragon instead of CFMX?
- Would you buy a support contract?
- Would you buy a subscription (like Red Hat Linux and JBoss offer)?
- Which open source license would you prefer? dual GPL/commercial (like MySQL)? LGPL (like Linux)? Apache (like Apache and Tomcat, and the rest of the Jakarta projects)?
I have to admit I still don't quite "get" open source in terms of it being a viable business model for software companies (though I see its value in other respects), so it's unlikely we'll go that route with BlueDragon. But I'd be interested in hearing what people have to say.