Lessons of Free Software History ● Paul Elliott ● ● Summary about what can be learned from Free Software history. ●

Slides:



Advertisements
Similar presentations
Overview of Free/Open Source Software for Librarians Eric Goldhagen
Advertisements

Free Beer and Free Speech Thomas Krichel
What is GNU/Linux (Not Linux!)? David Sudjiman davidsudjiman (at) yahoo (dot) com The latest version of this document can.
GNU / Linux A free operating system. Summary History What can you find on a Linux OS Linux Economy.
The Importance of Open Source Software Networking 2002 Washington, D.C. April 18, 2002 Carol A. Kunze Napa, California.
IS Spring The Basics of Open Source Reinhardi A. Haqi Mohamed Umar Shakeel Advanced Topics for Systems Development.
Ownership of Computer Software Ethical Questions and Concerns.
GNU, Linux and Open Source GNUKernel GNU/ Linux OpenSource.
Computers in Society The Computer Industry: Open Source.
Open Source/Free Software Source code is available Extensible Can be changed, modified Freely distributed Copies Modified versions Alternatives to commercial/proprietary.
Jul The New Geant4 License J. Perl The New Geant4 License Makes clear the user’s wide- ranging freedom to use, extend or redistribute Geant4, even.
Free Your Mind Code.  Sometimes I write software in exchange for money (don’t judge)  Sometimes I write software in exchange for knowledge, experience,
Introduction to Linux Chapter 1. Operating Systems Operating System (OS) - most basic and important software on a computer Performs core tasks Organize.
CHAPTER 6 OPEN SOURCE SOFTWARE AND FREE SOFTWARE
Version Control with Subversion. What is Version Control Good For? Maintaining project/file history - so you don’t have to worry about it Managing collaboration.
Copyright and Software and You. What is copyright? The Copyright Act of 1976 prevents the unauthorized copying of a work of authorship. – However, only.
 Open-source software ( OSS ) is computer software that is available in source code form: the source code and certain other rights normally reserved.
Licenses A Legal Necessity Copyright © 2015 – Curt Hill.
Computers and Society Examine the extent to which Richard Stallman’s GNU manifesto has succeeded in challenging the dominance of conventionally distributed.
Overview of Linux Dr. Michael L. Collard 1.
Operating Systems AOIT Principles of Information Technology.
Open Source Software In the beginning, all software was free –in the 1960s,when IBM and others sold the first large-scale computers, these machines came.
Maintainability of FLOSS Projects
CPS 82, Fall Open Source, Copyright, Copyleft.
Chapter 1: Welcome to Linux An intro to UNIX-related operating systems.
Free Software: History, Perspectives and Implications.
 Linux Mint is a computer operating system designed to work on most modern systems, including typical x86 and x64 PC’s. Linux Mint can be thought of.
Public Access: Update on Progress National Science Foundation April 2, 2014.
FP 501 OPEN SOURCE OPERATING SYSTEM CHAPTER 1: INTRODUCTION TO OPEN SOURCE SOFTWARE (OSS) TECHNOLOGY.
Open Source Software. Chris Moylan Group 5...I think.
Silberschatz, Galvin and Gagne ©2011 Operating System Concepts Essentials – 8 th Edition Chapter 2: The Linux System Part 1.
Getting the Best Video Quality When Shrinking a Blu-ray onto a Blank Bd25 Disc It is a deep tooted concept that whenever compression is needed in the process.
Effective IT solutions Using Open Source Software dr. comp. sci. Valdis Vītoliņš Odo Ltd, Latvian Open Technology Association Baltic Spark April
What Is Free Software and Open Source Software?. So, whats up here?
Free Software - Introduction to free software and the GPL Copyright © 2007 Marcus Rejås Free Software Foundation Europe I hereby grant everyone the right.
1 Open Source Software Licensing ● Bruce Perens, ● Perens LLC ● One of the founders of the Open Source movement in software.
The Linux Kernel Christoph Lameter, Ph.D. Technical Advisory Board The Linux Foundation.
The 5 Minute Blaggers Guide To Linux By Dan Lynch Made On Linux.
Localization by TDOA ©Thomas Haenselmann – Department of Computer Science IV – University of Mannheim Lecture on Sensor Networks Historical Development.
Opening Windows to a Wider World Why Samba moved to GPLv3 Jeremy Allison Samba Team
The hacker approach: the deve- lopment of free licenses IPNM 2007 Kaido Kikkas This document uses the GNU Free Documentation License (v1.2 or newer).
Copyright © Texas Education Agency, All rights reserved
What is F/LOSS? By Scot Henderson.
The hacker approach: the deve-lopment of free licenses
LINUX History In 1984 a project was launched by Richard Stallman to develop a complete Unix-like operating system that would be considered free software.
OPEN SOURCE.
Credit Score What is a credit report and why is it important to you?
Open Source software Licensing
Understanding Copyright
OPEN SOURCE.
Open Source Software in Academia
Selected topic in computer science (1)
What is Copyright?.
Lesson Objectives Aims You should be able to:
Copyright and Fair Use Guidelines
5.0 : Windows Operating System
BSD (Unix) vs. GNU/Linux
Linux Not in textbook.
Computer Law th class: Open Source.
Open Source Software Keenan Zuraiz
How saving now can help you get ahead tomorrow
Object Oriented Practices
FOSS 101 Sarah Glassmeyer Project Specialist Manager,
Ethics of Free Software
Chapter 2: The Linux System Part 1
Copyright 1. Infringement 4. Web Content 5. Orphan Works 6. Fair Use
FREE SOFTWARE DEFINITION
GNU General Public License (GPL)
APACHE LICENSE HISTORICAL EVOLUTION
Section 1: Linux Basics and SLES9 Installation
Presentation transcript:

Lessons of Free Software History ● Paul Elliott ● ● Summary about what can be learned from Free Software history. ● ●

Why does Linux and other Free software succeed? ● GNU/Linux is a fixin' to achieve world domination. ● Corporate theoreticians are in shock. ● How could this happen? ● What is happening? ● Why?

The Proprietary developers have not been idle. ● I don't know how many sucky versions of windoze and other proprietary software has come out. ● Billions of dollars have been spent paying proprietary developers. ● If the problem were a software coding method problem, why has it not been fixed? That is, why does proprietary software still suck? ● The answer is, it is not a software coding method problem, and it can not be fixed.

There is an answer from the history of free software. The answer is very simple. The answer repeats endlessly in many separate incidents.

Freedom works, control doesn't.

In almost every fork.... The “free” branch succeeded and the “control” branch failed.

If someone pays money to install a ring in your nose, is it smart to save on the cost of a hacksaw?

RMS is the hero who discovered the power of Freedom in Software ● Experiences at MIT caused his discovery. ● encoded discovery into GNU manifesto, GPL. ● Applied discovery in creating gcc, GNU utilities. ● Failed to apply discovery in HURD. ● By Jin Wicked

HURD failed. ● Used “Bondage and Discipline” OS development technique from academia called microkernel. ● HURD never advanced to the point it could be “set free”. That is, let many developers work on it “Bazaar” style.

LINUX succeeds. ● Without understanding RMS' principles, Linus applied them “just for fun”. ● Rejected the microkernel and other forms of B&D programming. ● Created something that ran quickly. ● Set it free, so that other developers could help (bazaar style).

LINUX succeeds. ● Only a small percentage of today's LINUX code was actually written by Linus. ● Linus uses sound judgment in deciding what contributed code to include. ● If others disagree, they are free to fork.

GNU/LINUX and other Free Software can not be controlled. ● If Linus (or any other free software author) were to go crazy or quit, other developers would inevitably take over, forking the project if necessary. ● Who are you going to sue, buy, or co-opt? No person or organization owns free software. Can MicroSuck sue to take away the free speech rights of thousands of free software developers scattered all over the globe? Source Code = speech. ● There is no central committee to mess things up or “compromise”.

The GPL protects GNU/LINUX ● Because of the so called “viral clause”, GNU/LINUX can not be attacked by embrace, extend, extinguish. ● GPL provides that any extension must be GPLed. (“viral clause”) ● Therefore if the extension contains any positive features, these features can be embraced by the original branch! So extinguish does not work!

Nightmare scenario ● If by chance, one of the BSDs had become the dominant free OS instead of LINUX, it would have been already attacked by MS using embrace, extend, and extinguish.

Nightmare scenario ● That is, MS would have created a windows/BSD hybrid capable of running both windows and BSD programs. As time went on, the BSD side of this monstrosity would have been “extended” thereby “extinguishing” the original BSD!

The GPL stops hybrid monster creation! ● If proprietary code is mixed with GPLed code, in a distributed product, then by the terms of the GPL, that proprietary code must be released under the GPL. ● This is totally unacceptable to proprietary developers. The proprietary nature of their code is the indispensable basis of all of their tricks and traps and it is the only reason they get paid! To them, it is sine qua non. ● This stops hybrid monster creation. ● It is also the true reason that the GPL is hated by proprietary developers and their lackeys!

Free software is a spontaneous order. ● Ancient Chinese philosopher Chuang-tzu may have been first to discover theory of “spontaneous order”. Friedrich Hayek is the first modern advocate of the theory. ● Other examples spontaneous orders. – Natural languages. (only the French seek to control the development of language, proof that it is a bad idea.) – Free markets – developed in antiquity – Organic evolution itself!

Free Software recipe for success. ● Let go of the urge to control. ● Don't use “bondage and discipline” techniques. ● Create something that runs quickly. ● Set it Free, accepting the input from many other developers. ● Guide the result. If others disagree, they are free to fork. ● Let Freedom Ring!

copyright ● This document contains a number of trademarked logos. They are included by virtue of fair use. I obviously, do not hold the copyright to those logos. If you copy this document, you are responsible to insure that your use of those logos is fair use. ● The rest of this document is – Copyright (c) 2008 Paul Elliott. – Permission is granted to copy, distribute and/or modify this document – under the terms of the GNU Free Documentation License, Version 1.2 – or any later version published by the Free Software Foundation; – with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. – A copy of the license is included in the section entitled "GNU – Free Documentation License".