[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Some hard numbers on licenses used by elisp packages
From: |
Richard Stallman |
Subject: |
Re: Some hard numbers on licenses used by elisp packages |
Date: |
Mon, 17 Jul 2017 08:00:34 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> What is the motivating factor for the authors who have not assigned any
> license to their package? That open source software should be covered bye
one
> clearly stated open source license?
I suspect part of the cause is the influence of the "open source"
idea.
In the free software movement, the point a free program is to give
users freedom. The license is what gives users that freedom, so the
choice of the best free license is a very important question, and
applying the license properly is crucial.
The "open source" idea tends to make "good code" the highest value,
and treats "giving users freedom" as secondary. While the original
leaders of open source treated licenses as important, the ideas have
evolved over the last ten years to dismiss licenses as a minor detail.
Under the malign influence of GitHub, developers often don't bother to
put on a license. This means the program is not free software (nor
open source either).
https://gnu.org/philosophy/open-source-misses-the-point.html explains
the difference between free software and open source, especially at
the level of ideas.
This is part of why, in the GNU Project, we never use the term "open
source" to describe what we are doing.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
- Re: Some hard numbers on licenses used by elisp packages, (continued)
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/13
- Re: Some hard numbers on licenses used by elisp packages, Jonas Bernoulli, 2017/07/14
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/15
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/15
- Re: Some hard numbers on licenses used by elisp packages, Jean-Christophe Helary, 2017/07/15
- Re: Some hard numbers on licenses used by elisp packages, Jonas Bernoulli, 2017/07/16
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/16
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/16
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/17
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/17
- Re: Some hard numbers on licenses used by elisp packages,
Richard Stallman <=
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/17
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/18
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/23
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/27
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/28
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/29
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/29
- Re: Some hard numbers on licenses used by elisp packages, Mats Lidell, 2017/07/29
- Re: Some hard numbers on licenses used by elisp packages, Ivan Andrus, 2017/07/29
- Re: Some hard numbers on licenses used by elisp packages, Richard Stallman, 2017/07/30