From: Karl Fogel <kfogel@red-bean.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: rms@gnu.org, Mats Lidell <mats.lidell@cag.se>, emacs-devel@gnu.org
Subject: Re: Some hard numbers on licenses used by elisp packages
Date: Fri, 28 Jul 2017 15:36:45 -0500 [thread overview]
Message-ID: <87y3r8mh7m.fsf@floss> (raw)
In-Reply-To: <874ltwbzpl.fsf@bernoul.li> (Jonas Bernoulli's message of "Fri, 28 Jul 2017 12:52:38 +0200")
Jonas Bernoulli <jonas@bernoul.li> writes:
>Github actively encourages users to specify the license. (Yes, they
>suggest free software as well as open source licenses.)
There's a difference?
If you're thinking that "free software" == "copyleft" and "open source" == "non-copyleft", that's actually not the case. For example, the GPL is both a free software and an open source license, and the same is true of (say) the MIT license.
This FAQ item at the OSI explains this in more detail: https://opensource.org/faq#free-software. (I believe that FAQ entry explains it in such a way that the FSF would agree with the facts & history as presented there, although perhaps not with the philosophical equivalence implied.)
I completely agree with you that GitHub now actively encourages people to apply a free software license when publishing their code. GitHub does this both via UI nudges and via their public posts and comments on the topic (see https://help.github.com/articles/licensing-a-repository/ for example).
-Karl
next prev parent reply other threads:[~2017-07-28 20:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 14:29 Some hard numbers on licenses used by elisp packages Jonas Bernoulli
2017-07-12 12:49 ` Jonas Bernoulli
2017-07-13 12:23 ` Richard Stallman
2017-07-14 19:44 ` Jonas Bernoulli
2017-07-15 19:38 ` Mats Lidell
2017-07-16 1:55 ` Richard Stallman
2017-07-16 2:20 ` Jean-Christophe Helary
2017-07-16 15:41 ` Jonas Bernoulli
2017-07-16 17:37 ` Mats Lidell
2017-07-16 22:17 ` Mats Lidell
2017-07-17 12:00 ` Richard Stallman
2017-07-17 12:00 ` Richard Stallman
2017-07-17 12:00 ` Richard Stallman
2017-07-17 21:23 ` Mats Lidell
2017-07-18 14:16 ` Richard Stallman
2017-07-23 22:14 ` Mats Lidell
2017-07-27 22:50 ` Mats Lidell
2017-07-28 17:16 ` Richard Stallman
2017-07-29 12:19 ` Mats Lidell
2017-07-29 19:09 ` Richard Stallman
2017-07-29 19:54 ` Mats Lidell
2017-07-29 22:49 ` Ivan Andrus
2017-07-31 0:46 ` Richard Stallman
2017-07-31 17:48 ` Achim Gratz
2017-08-08 1:02 ` Ivan Andrus
2017-07-31 0:51 ` Richard Stallman
2017-08-01 21:46 ` Mats Lidell
2017-08-02 1:54 ` Stefan Monnier
2017-08-03 19:42 ` Richard Stallman
2017-08-03 19:58 ` Stefan Monnier
2017-07-28 10:52 ` Jonas Bernoulli
2017-07-28 17:16 ` Richard Stallman
2017-07-28 17:47 ` Jonas Bernoulli
2017-07-28 17:16 ` Richard Stallman
2017-07-29 13:48 ` Jonas Bernoulli
2017-07-29 19:10 ` Richard Stallman
2017-07-29 19:10 ` Richard Stallman
2017-07-28 20:36 ` Karl Fogel [this message]
2017-07-29 19:07 ` Richard Stallman
2017-07-31 0:49 ` Richard Stallman
2017-07-17 11:59 ` Richard Stallman
2017-07-28 11:17 ` Jonas Bernoulli
2017-07-29 14:54 ` Mats Lidell
2017-07-29 19:09 ` Richard Stallman
2017-07-29 19:06 ` Richard Stallman
2017-07-29 19:06 ` Richard Stallman
2017-07-29 20:07 ` Mats Lidell
2017-07-30 6:28 ` Jean-Christophe Helary
2017-07-31 16:03 ` Jonas Bernoulli
2017-07-31 17:03 ` Jonas Bernoulli
2017-08-03 9:35 ` Mats Lidell
2017-08-03 19:50 ` Richard Stallman
2017-07-13 12:23 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3r8mh7m.fsf@floss \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=mats.lidell@cag.se \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).