This exercise is available at https://study.find-santa.eu/exercises/cs/licensing/.
For the sake of the environment, please avoid printing these instructions in the future. Thank you!

OSS Software Licensing & Dependencies

Research the answer to your questions for max. 25 minutes. This also includes preparing a 5 minute presentation for your classmates.

Team 1

You're coding a hobby project and are not yet sure how to deal with the license. Consult (and introduce to the others) choosealicense.com .

  1. What is the legal situation when you publish the project without adding any software license?
  2. Which one would you choose? Why?

Team 2

You publish your project as open source software. You want to allow others to use it as open source software, but want to make sure that nobody will sell your software as part of their product. You also want to make sure that patches and upgrades by the community are returned to your project.

  1. Which licenses are reasonable options?
  2. What applies to people using your project as part of their SaaS solution?

Team 3

You're working on proprietary software that is installed on your customer's computers. You want to save a lot of time and money by using open source software libraries (instead of reinventing the wheel or using expensive alternatives with a vendor lock-in).

  1. What considerations should you take into account before adding a new dependency?
  2. Which licenses are ok for you to use and which ones are problematic?

Team 4

You're working on a proprietary SaaS solution. You want to save a lot of time and money by using open source software libraries (instead of reinventing the wheel or using expensive alternatives with a vendor lock-in).

  1. What considerations should you take into account before adding a new dependency?
  2. Which licenses are ok for you to use and which ones are problematic?

Team 5

You’re working on a well established, proprietary SaaS solution that employs many open source software licenses. You have a strict policy in place with regard to which licenses are OK to use and which aren't.

  1. How do you enforce this policy?

Team 6

Your project team has decided to use the Apache License version 2.0 for your node.js software.

  1. How would you communicate this to the rest of the world?
  2. Which files need to be edited at the very least?
  3. What are best practices?