Technology news and Jobs 
Our Blogs Open Sauce GPL: why can't a lawyer understand it?
Our Blogs Open Sauce GPL: why can't a lawyer understand it? | GPL: why can't a lawyer understand it? |
|
| by Sam Varghese | |
| Tuesday, 10 June 2008 | |
|
Page 2 of 2 In 1998, the Open Source Iinitiative was begun by Eric Raymond and Bruce Perens in order to make free software more appealing to businesses. Featured Whitepaper
5 Best Practices for Smartphone Support
According to a research paper put out by market services firm Vision Mobile, "where the OSI and the FSF diverge is that the OSI also require that an OSI approved open source license should not restrict commercially important freedoms, such as the ability to distribute open source and non open source software together, and to not discriminate against any persons, field of endeavour or technology products." When the GPLv2 was written, software patents were uncommon and software licensing was in its infancy. Over the years, as innovations in software have grown less - mainly because you can't invent something twice - companies have sought to gain a business advantage by taking out patents on what they deem to be their inventions. Some of these "inventions" are laughable and patent offices around the world have granted some ridiculous patents in their time. Hence, after a long period of consultation, Stallman and lawyer Eben Moglen released the GPLv3 to plug some loopholes in the GPLv2. Are there incompatibilities between open source software and many business models as Walsh claims? Sure, if you violate the terms of the licence of any software, you will have to pay for it. It doesn't matter if it's open source or closed source. Microsoft has paid out so often for using other people's code that I've lost count of the number of times it has done so. The casual reader will skim through what Walsh has written and come away with the impression that the man has said nothing apart from the fact that proprietary software companies should be careful as to how they use open source code. That has always been the case and will continue to be the case. But there are also insidious statements like this: "Any activity that leverages software for business advantage is likely to restrict the software's freedom..." Nope, you can take open source code, modify it to your heart's content and use it within the portals of your company and you would not have violated any licence. You cannot be touched. It's only when it comes to distributing the code, that the licence cuts in - you need to release all of it. Under the GPL, you can write your own code which is dynamically linked to the original code - and you do not have to release the entire lot. If GPL code is statically linked to non-GPL code, then the latter constitutes a derivative work and you need to release all the code if you are distributing the product. Walsh is of the opinion that it would be better if GPL violation cases went to court so that there was some precedent to go by. Of course, he forgets to tell us that it would also ensure that a number of lawyers would be able to bill X number of hours for representing this client or that. Settling a case outside court does not enrich lawyers as much as a prolonged trial does. Have a look at this list of settlements, Walsh, and calculate how much it has cost your profession. Let me leave it there. If Walsh was really trying to make a point, he would have followed the fundamental rule that lawyers do: see what kind of case your opponents have and then draft your own defence. All that he appears to be trying to do is to confuse people and leave one impression - free and open source software is like dynamite. It's best left alone, you never know when it might blow up in your hands. |
Tags
| < Next story in category | Previous story in the category > |
|---|
