Copy-left and Copy-right

AAS 225 short talk.

Abstract:
Any discussion of open licensing almost invariably devolves into a debate between copy-left licenses and permissive licenses, both sides defending their views with a nearly religious fervor. Copy-left licenses, typified by the GPL family of licenses, require all derived products to maintain the open, GPL license. Permissive licenses, typified by the BSD family of licenses, do not impose such requirements. I’ll briefly explore the common arguments put forth in favor of either approach, and discuss some concrete examples of where these approaches have helped or hindered the software packages that used them.

Transcript

1. Copy-left and Copy-right what you need to know Jake VanderPlas AAS 225, January 2014
2. First of All… Always License your Code! (Everyone will Agree)
3. “If you stumble across some code with no attached licensing information, copyright laws would have you treat it as ‘all privileges retained’, even if its author in fact was just trying to make it available with no strings attached.” Arto Bendican http://ar.to/2010/12/licensing-and-unlicensing
4. https://www.gnu.org/philosophy/free-sw.html -  the freedom to use the software for any purpose -  the freedom to change the software to suit your needs -  the freedom to share the software with your friends and neighbors -  the freedom to share the changes you make Free Software… Free as in Freedom, not Price
5. Permissive - or - Non-permissive?
6. BSD/MIT-style - vs - GPL-style?
7. So What’s the Difference? BSD/MIT “Sticky” or “ Viral” license If software incorporates/builds on any GPL-derived code, then the entire package must be GPL-licensed.   “Permissive” license Derived software is free to have any license: code can be incorporated in closed projects.   GPL
8. This difference leads to a surprising amount of contention.
9. Why Use One Over Another? GPL-style: -  Free software should stay free. -  Software provenance & attribution maintained. -  Unfair for private entities to profit from free and open community effort. BSD-style: -  Licensing restrictions on derived software are against the “Free” philosophy. -  Attribution should not be guaranteed by a legal statement, but by academic norms. -  Ability of private entities to adapt code leads to upstream contribution.
10. BSD-style GPL-style
11. For More Information and references on licensing, see my AstroBetter blog post, The Whys and Hows of Licensing Scientific Code http://www.astrobetter.com/ the-whys-and-hows-of-licensing-scientific-code/ Email:  jakevdp@uw.edu     Twi3er:  @jakevdp     Github:  jakevdp     Web:  h3p://www.vanderplas.com     Blog:  h3p://jakevdp.github.io