Choosing A License
|Title||Choosing A License|
|Overview||Student will choose a license for a hypothetical software project based on criteria given|
|Prerequisite Knowledge||Should have had an introduction to intellectual property as it relates to software and to open source licenses. Completing Finding_the_License first would be valuable, as this exercise requires finding the license for existing software.|
|Learning Objectives||Students will be able to assess some of the criteria involved in selecting a software license; however, when in doubt (and especially when in doubt and using other's code), a lawyer should be consulted.|
Every piece of software your students write should have a license, so it's a good habit to instill early on. In addition, since any novel and unique artistic work is considered copywrited when fixed in a medium (vast oversimplification, but it will do for this purpose), unless coders choose a license, their software is copywrited upon creation.
Good background reading:
For each of the following hypothetical scenarios, research and choose an appropriate license. Choose A License is a good place to start, but will not answer all questions.
- You have written a piece of software and want anyone to be able to use it for anything they'd like to, but you want to have attribution if someone else uses your work. You also want to make sure that you don't give people the impression that you're implying a warranty.
- You have a photograph and you'd like people to be able to use it, as long as they give you credit and don't use it for commercial purposes.
- You've written a piece of software and wish to retain all rights to it.
- You've written a piece of software based on GIMP but with some changes, and you'd like to start distributing your version.
- You have written a piece of software and:
- want anyone to be able to use it for anything they'd like to
- want to have attribution if someone else uses your work
- want to make sure that you don't give people the impression that you're implying a warranty, and
- want to ensure that if someone contributes to the project that they then don't sue you for patent infringement.
Document which license you'd choose in each scenario and your rationale for that choice.
The student will turn in the list of projects, licenses and rationales.
Grading can be based on: 1) Obtaining a correct answer for the license *and* 2) Identifying the rationale for choosing that license.
- This activity can be completed individually or in small groups.
- For several of the questions, there may be more than one license that will work (legal stuff = not always simple ;-) Encourage your students to choose the simplest possible answer that they can find from among the commonly accepted open source licenses (the ones listed at Choose A License are a good start).
- If students have different answers you can have a discussion about what factors led to each choice.
|Knowledge Area/Knowledge Unit||Social Issues and Professional Practice (SP) / Intellectual Property|
|Topic||Intellectual property rights|
|Level of Difficulty||Is this activity easy, medium or challenging?|
|Estimated Time to Completion||How long should it take for the student to complete the activity?|
|Materials/Environment||What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?|
|Source||Is there another activity on which this activity is based? If so, please provide a link to the original resource.|
|License||This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License|
Suggestions for the Open Source Project:
It would be helpful if your project had some explanation of it is licensed the way it is. Also, if there's someone in your community who has experience with choosing licenses for projects that would be willing to speak with the class (via Skype or IRC) that would be a great thing to offer.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License