Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Hey Kid! Don't Copy That Floppy! (Rubyfuza Edition)

Aaron Kalin
February 07, 2013
170

Hey Kid! Don't Copy That Floppy! (Rubyfuza Edition)

Software licensing sets up rules for everyone to follow when contributing or using code. Some companies have specific policies on what types of licenses they allow in their code base. Some companies also put rules on their developers for how they're allowed to contribute to software. Got a licence for your code? We'll discuss why you need one and go over some popular options before you end up on the wrong side of a DMCA notice.

Aaron Kalin

February 07, 2013
Tweet

Transcript

  1. This talk is provided for informational purposes only to get

    you thinking about software licensing. Although I [Aaron Kalin] will attempt to give accurate information in this talk. You should consult a professional attorney to verify information given in the following talk. Anything I say in this talk should not be offered as legal information. I am not an attorney! Legal Disclaimer
  2. [brief] History of Copyrights 1866 “Berne Convention for the Protection

    of Literary and Artistic Works” Signing countries agree to recognize each others copyrights
  3. [brief] History of Copyrights 1866 “Berne Convention for the Protection

    of Literary and Artistic Works” Signing countries agree to recognize each others copyrights Granted a minimum of 50 years on copyrighted work
  4. [brief] History of Copyrights 1866 “Berne Convention for the Protection

    of Literary and Artistic Works” Signing countries agree to recognize each others copyrights Granted a minimum of 50 years on copyrighted work You are automatically granted copyrights on an original work
  5. [brief] History of Copyrights 1992 The Agreement on Trade Related

    Aspects of Intellectual Property Rights (TRIPS)
  6. [brief] History of Copyrights 1992 The Agreement on Trade Related

    Aspects of Intellectual Property Rights (TRIPS) Programmers aren’t the only ones who can come up with huge acronyms
  7. [brief] History of Copyrights 1992 The Agreement on Trade Related

    Aspects of Intellectual Property Rights (TRIPS) Programmers aren’t the only ones who can come up with huge acronyms Adopted virtually everywhere in the world
  8. [brief] History of Copyrights 1992 The Agreement on Trade Related

    Aspects of Intellectual Property Rights (TRIPS) Programmers aren’t the only ones who can come up with huge acronyms Adopted virtually everywhere in the world Similar to Berne Convention
  9. Open Source Licenses Forms of Copyrights Copyright License Copyright Assignment

    “rental” copy can’t modify (without permission)
  10. Open Source Licenses Forms of Copyrights Copyright License Copyright Assignment

    “rental” copy can’t modify (without permission) “assign” ownership
  11. Open Source Licenses Forms of Copyrights Copyright License Copyright Assignment

    “rental” copy can’t modify (without permission) “assign” ownership can modify (restrictions may apply)
  12. Open Source Licenses Patents You can patent code This is

    a grey legal area, but something to watch out for in code
  13. Open Source Licenses Patents You can patent code This is

    a grey legal area, but something to watch out for in code Don’t feed the patent trolls
  14. Open Source Licenses Contributor License Agreement (CLA) “Assigns” contributor copyrights

    to original author or organization Keeps the playing field level for everyone
  15. Open Source Licenses Why license? Allows for contributions without violating

    your copyright Allows your business to benefit from open source contributions
  16. Open Source Licenses Why license? Allows for contributions without violating

    your copyright Allows your business to benefit from open source contributions Helps control distribution once its out there
  17. Open Source Licenses Creative Commons Copyleft option (Share Alike) No

    patent protections Protects author and contributors
  18. Open Source Licenses Creative Commons Copyleft option (Share Alike) No

    patent protections Protects author and contributors Can set non-commercial usage restrictions
  19. Open Source Licenses GPL (v3) Contributors can set their own

    license terms Dual licensing options Patent protections
  20. Open Source Licenses GPL (v3) Contributors can set their own

    license terms Dual licensing options Patent protections Anti-Circumvention protections
  21. Open Source Licenses GPL (v3) Contributors can set their own

    license terms Dual licensing options Patent protections Many related versions (LGPL, AGPL, etc) Anti-Circumvention protections
  22. Open Source Licenses Apache 2.0 “Contributors” also license their work

    under Apache 2.0 Must preserve copyright notices in derivative works
  23. Open Source Licenses Apache 2.0 “Contributors” also license their work

    under Apache 2.0 Must preserve copyright notices in derivative works Compatible with GPL (v3 only)
  24. Open Source Licenses Can haz license? Review license details before

    choosing Include a LICENSE file along with a notice in your README
  25. Open Source Licenses Can haz license? Review license details before

    choosing Include a LICENSE file along with a notice in your README If your license allows, consider a Contributor License Agreement
  26. Open Source Licenses Can haz license? Review license details before

    choosing Include a LICENSE file along with a notice in your README If your license allows, consider a Contributor License Agreement Urge other non-licensed projects to adopt a license so you can contribute (legally)
  27. Your rights Only certain licenses are compatible with your code

    Many companies have “rules” about software licensing:
  28. Your rights Only certain licenses are compatible with your code

    Many companies have “rules” about software licensing: Your contract may prevent you from contributing to open source
  29. Your rights The Digital Millennium Copyright Act (DMCA) Allows enforcement

    of copyright claims in the United States You can wield this power too! (but, with great power comes great responsibility)
  30. Your rights What’s your price? Any work you create for

    me Any work you create during non-work hours I get to own
  31. Your rights What’s your price? Any work you create for

    me Any work you create during non-work hours Rights to the names of things you create I get to own
  32. Your rights What’s your price? Any work you create for

    me Any work you create during non-work hours Rights to the names of things you create I get to own Own any previously created works you modify while on the job
  33. Review your contract with an attorney to understand your rights

    License your code if you haven’t already! Recap
  34. Review your contract with an attorney to understand your rights

    License your code if you haven’t already! Read your software licenses. Its all about the level of control you want. Recap
  35. Review your contract with an attorney to understand your rights

    License your code if you haven’t already! Read your software licenses. Its all about the level of control you want. Recap Encourage unlicensed open source projects to adopt a license.