This week, i wandered into the Information Architecture Meetup. Out of interest – the concept of Information architecture is still somewhat fuzzy to me (mainly because i don’t know much about it). The subject presented was interesting: open source licenses, as presented by an IP-IT lawyer, Ywein Van Den Brande.
There are two main open source categories: the copyleft licenses and the non-copyleft licenses. Copyleft means the license is contagious: if you modify the code, or add on to it, the license must be extended to your code.
The well-known ones in copyleft land:
- GPLv2 and v3: V3 is somewhat stricter than v2. Difference: v3 allows you to use any means to access GPL’ed code hidden in an appliance without breaching the license. It also makes it more difficult to patent GPLed code.
- Lesser GPL: softer form of GPL
Non-copyleft:
Both very light – and can be used in proprietary software.
Others I know (not mentioned in the presentation), brought out by organizations to fit their requirements:
- MIT License: a bit like BSD license
- Ruby license
- Mozilla Public license
- Apparently Google is going to come out with one too.
All open source license have it in common that they offer no warranty and the authors are not liable for any problems issuing from using their code.
An interesting twist: if you sell something in Belgium, you are responsible. So whatever your license, you’re still liable to get sued over bad code.
Text, designs and pictures fall under another open license: Creative Commons. By default, any original content you produce falls under copyright, unless you indicate, with Creative Commons, that you are willing to relinquish some of your rights.
There’s different Creative Commons licenses, corresponding to degrees of freedom:
- Attribution (by): you authorize any person to use your material, if they make a reference to you
- NonCommercial (nc): your material can not be sold
- ShareAlike (sa) aka copyleft: anything reusing your material must have the same license
- NoDerivs (nd): you may copy, distribute, display and perform the work itself, but not modify it
It was a good presentation. All the more because I think this knowledge is essential if you want to make a living working with open source.