CSC 379:Week 2, Group 5

GNU General Public License

Overview

The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well. Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL. It ensures that any software that was derived from open source remains available to the general public and freely distributable.

• GPL - Version 1.0, February 1989
  • To guarantee the freedoms to share and change free software.
  • To make sure the software is free for all its users.
• GPL - Version 2.0, June 1991
  • Further restricted rights from Version 1.0
  • Updated to cover distribution of the program or programs as a whole.
  • Linux kernel released under this license version
• GPL - Version 3.0, January 2006
  • Further restricted rights from Version 2.0
  • Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.
  • Main purpose, the abolition of DRM as a social practice.

Discussion Questions

What is the impact of GPL use?

In general GLP software will impact certain groups, companies, or organizations differently and others in the same manner. The following sections will present different views of the impact

• Personal Software Users
  • Positive impact: The reduced monetary cost to acquire and use of software to achieve a personal task or action.
  • Negative impact: The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features.
• Developers - Open Source
  • Positive impact: To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement.
  • Negative impact: An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.
• Developers – Commercial
  • Positive impact: Developer can investigate and analyze already used and solved approaches to a problem and their core issues.
  • Negative impact: Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.
• Commercial Software Companies
  • Positive impact: Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.
  • Negative impact: Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.
• Non-profit organizations
  • Positive impact: A community may be experienced and willing to provide a good solution or product to keep the operating cost down.
  • Negative impact: Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.
• Government
  • Positive impact: The Government may be able to replace commercial software with open source counterparts to save money and increase profits.
  • Negative impact: Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.
• Education and Research
  • Positive impact: A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.
  • Negative impact: The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.

What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?

The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet. While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to. This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements. If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect. At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group. The main ethical issue is the amount of power given to the writers of the license and how it is used.

What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?