Copyright vs. copyleft licensing

*Let me begin by apologizing for the lack of completeness in this article. Soon…*
Last updated: January 17, 2016 at 8:54 am

Intellectual property, voluntary contracts and copyright vs copyleft licensing are paramount to organic technological freedom. A couple of years ago, I would have reeled at that sentence, but now, I try to live it.

Statute of Anne

First ammendment protections.

Eighth ammendment protections.
Article VIII

Excessive bail shall not be required, nor excessive fines imposed, nor cruel and unusual punishments inflicted.

Copyright licensing and patents are a very important aspect to consider when using or creating software and content. We need to mind these topics so we make wise decisions and hopefully stay out of trouble.


Here is a good article from Smashing Magazine outlining copyleft licenses.

The ‘BSD-like’ licenses such as the BSD, MIT, and Apache licenses are extremely permissive, requiring little more than attributing the original portions of the licensed code to the original developers in your own code and/or documentation.

The GPL license imposes similar obligations as the BSD-like licenses, but one major difference persists. The GPL license is ‘viral,’ meaning any derivative work you create containing even the smallest portion of the previously GPL licensed software must also be licensed under the GPL license.

The five most common open source licenses in order of least to most restrictive.

A practical guide to GPL compliance.
An expansive list of open source licenses.


Obviously, there is a lot more to come.

Leave a Comment

Your email address will not be published.

Time limit is exhausted. Please reload CAPTCHA.