Differences between European and U.S. adoption of open source
In my role as pseudo general counsel at Alfresco, I wade through a lot of contracts. As part of this, I'm constantly trying to find the right balance between the needs of our customers and partners in different geographies.
Interestingly, our European and North American customers view licensing very, very differently. Generally speaking, our European customers want our software under an open-source license (GPLv2). North Americans? They want the benefits of open source without the obligations and perceived risk (meaning, they prefer a dual-license approach that allows them to contribute back modifications if they wish, but not out of duty).
I've been trying to figure out why the two geographies, surrounded only by the Atlantic Ocean, have such different perspectives on licensing. I believe it comes down to this: governments versus private corporations.
Throughout Europe governments lead the adoption of open-source software, and Alfresco has been widely adopted by governments throughout Europe. In my experience, government IT workers (especially in Europe) tend to buy into the ideals of open source more fully than their private-sector counterparts. They're looking for open platforms upon which the vendor and buyer can collaborate. They trust the GPL and seek out its obligations.
This is somewhat less true of North America, where most open-source adoption is driven by enterprises seeking to lower costs and maximize innovation. In my experience, their developers buy into the ideals of open source but their legal departments generally do not, largely because their understanding of the risks and obligations of open source remain anemic, though it's getting better. So these buyers (or, at least, their legal departments) tend to want contracts that look like the Old World of software. They prefer dual licensing when they can get it as a way to mitigate perceived risks. In other words, they want the benefits of open source without worrying about possible obligations.
Your experience may differ from mine, but I've canvassed opinion on this and have found that others largely share my experience. This means that if you're hoping to do business in Europe and North America, you need to be prepared for the differing approaches to open-source licensing, contracts, indemnification (Europe cares much less about it than the United States does), etc.
And given that open-source businesses are almost of necessity global businesses, you'd be wise to get ready for this difference in views sooner rather than later. Consider yourself warned.
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.





If I was hungry, last thing I care about is what is written in that license agreement that they make me agree to (by signing with my blood). I want my lunch. I don't care about its terms and thus whether it's agreeing to be a slave or an employee. I mean, if I need this meal, I have to agree, otherwise they won't give it to me. A bit stupid?
There are Open Licensing with "obligations to give back" (GPL) and "without obligations" (Apache, BSD).
What kind is the prefered/objected in Gov/Bus in EU/NA?
-
by Ian Skerrett
December 19, 2007 1:43 PM PST
- It is interesting that the EU has also created their own open source license. http://ec.europa.eu/idabc/en/document/6523
-
Reply to this comment
-
(8 Comments)http://en.wikipedia.org/wiki/European_Union_Public_Licence