Middleware and Open Source Aren't a Perfect Match

Share it on Twitter  
Share it on Facebook  
Share it on Linked in  

IT Business Edge contributor Loraine Lawson recently interviewed Craig Muzilla, vice president of JBoss, Red Hat's middleware division. In that conversation, he addresses open source licensing concerns. He says the one license that causes the most problems for middleware is the General Public License.


"A requirement for General Public License is if you've modified code or added codes, if you add some of your own capabilities, you're committed to then submit that same code you have created in the same license you have to make it available - available as GPL into the original project. They call that upstream," Muzilla said. "So for an application developer, let's say maybe an ISV (independent software vendor) that is creating an application and they want to sell it, but they want to use some open source components underneath. Even an end-user company - it could be Bank of America or General Motors or whoever is creating applications based on some of these tools - would have an obligation under the GTL to submit the code back. I think it becomes a very, very gray area."


Muzilla said that it's a gray enough area that if you are concerned about intellectual property, you may think twice before using some of these licensing mechanisms.


Open source issues are a common concern and some of the Knowledge Network documents address topics in that area, including Open Data Standards, Linux Kernel and OS Interoperability.


What areas of open source cause you the greatest concern? Are there any documents or tools regarding open source that you would like to see in the Knowledge Network?


For the latest Knowledge Network updates, follow us on Twitter.