DPS909 & OSD600 Winter 2018

Week 1

• Course introduction
  • DPS909
  • OSD600

• Some questions:
  • When you hear "open source," what comes to mind?
  • On a scale from 1 (not at all) to 5 (very)...
    • How comfortable are you working with technology you've never seen before?
    • How curious are you about how things work?
    • How likely are you to stick with a problem when it gets hard to solve?
    • How likely are you to ask for help when you get stuck?
    • How likely are you to pause your own work in order to help someone else who is stuck?
    • How self-motivated are you?
    • How self-directed are you?

• How to have Success in this course:
  • Willingness to be lost and not panic
  • Willingness to put yourself out there, jump in
  • Curiosity
  • Being driven, persistence
  • Willingness to ask for help
  • Willingness to give others help
  • Independent learning
  • Doing more than the bare minimum

• Discussion
  • Open Source Turns 20
  • Move Over Bay Street: Toronto's Burgeoning Tech Scene Is Taking Over
  • Open source professionals are more in demand than ever
  • How to get an open source job

• Let's talk about Copyright and Open Source Licenses
  • • IANAL: "I Am Not A Lawyer"
    • We're going to explore licensing from the POV of a developer participating in open projects

• Copyright (Copyright in Canada video)
  • Who created it, "owns" it.
  • Set of exclusive rights granted to the work's creator
  • "The right to copy," to produce or reproduce a work or substantial portion thereof
  • Copyright is automatic when a work is created, you don't have to register it.
  • Copyright in Canada
  • Copyright Guide
  • In a software project, there can be many copyright holders (e.g., many contributors), or all contributors may assign their copyright to the project (e.g., CLA, which we'll cover later)

Week 2

• Licenses
  • Rights, privileges, responsibilities, etc. applicable to someone other than the work's creator
  • "Terms and Conditions"
  • These must be granted by a copyright holder

• No License
  • What can you do with code you find that has no license?
  • what can I, can't I do?

• Public Domain
  • SQLite, which is now used by literally everybody, see http://www.sqlite.org/famous.html
  • Unlicense

• Consider some proprietary/closed End User License Agreements (EULA)
  • Richard Dreyfuss reads the iTunes EULA
    • Part 1: Please Read (.mp3)
    • Part 2: Responsibility (.mp3)
    • Part 3: Damages (.mp3)
    • Part 4: Effective Until (.mp3)
  • Spotify EULA

• Open Source Licenses
  • The Open Source Definition
  • Approved licenses by the Open Source Initiative: https://opensource.org/licenses
  • Choose a License: https://choosealicense.com/

• Learning Licenses: BSD
  • Family of Licenses, including 2-Clause BSD, 3-Clause BSD (aka New BDS), 4-Clause BSD
  • "Why you should use a BSD style license for your Open Source Project"
  • BSD Licenses code is usually compatible with other open/closed code, when you want to mix them.
  • Example software projects licensed under the BSD License:
    • Many Google Projects, including V8, Chromium, Go
    • D3.js
    • Django
    • nginx
    • Vi
    • Facebook uses a modified version of the 3-Clause BSD they call [BSD + Patents license]. This has been controversial
      • BSD + Patent
      • PATENTS in React
      • https://code.facebook.com/posts/112130496157735/explaining-react-s-license/
  • Summary:
    • You need to retain the license and copyright notice
    • You can use it commercially or non-commercially (privately)
    • You can distribute it freely
    • You can modify it freely

• Lab 1