all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Amin Bandali <aminb@gnu.org>
Cc: rms@gnu.org, dgutov@yandex.ru, emacs-devel@gnu.org,
	kaushal.modi@gmail.com, Eli Zaretskii <eliz@gnu.org>,
	john@yates-sheets.org
Subject: Re: Three cheers for Eli!
Date: Mon, 04 Jun 2018 10:30:09 +0200	[thread overview]
Message-ID: <87efhnar8u.fsf@mbork.pl> (raw)
In-Reply-To: <87602z2l3x.fsf@aminb.org>


On 2018-06-04, at 07:09, Amin Bandali <aminb@gnu.org> wrote:

> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> Out of curiosity: why aren't GNU projects open-source?  I know RMS
>> dislikes the term, but the source of GNU projects is available on the
>> Internet, so technically they should count, no?
>
> GNU projects are licensed under the GPL.  Though GPL is an "OSI
> approved" license, and so technically an "open source" license,
> calling it that comes way short of conveying what it stands for.
>
> Instead of attempting to explain it myself, I'll refer you to
> this [0] article by RMS, called Why Open Source misses the point
> of Free Software, which explains it much better than I could.

I understand that, but Eli said

> There's no doubt open-source projects do
> exist, it's just that GNU projects are not among them.

I thought that GNU projects are rather in the intersection of "free
software" (in FSF sense) and open-source.  That sentence confuses me.

Best,

--
Marcin Borkowski
http://mbork.pl



  reply	other threads:[~2018-06-04  8:30 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 17:42 Three cheers for Eli! Alan Mackenzie
2018-05-28 18:17 ` Eli Zaretskii
2018-05-28 19:39 ` Clément Pit-Claudel
2018-05-28 20:29   ` John Wiegley
2018-05-30 10:29     ` Van L
2018-05-28 19:45 ` Óscar Fuentes
2018-05-29  1:30 ` Stefan Monnier
2018-05-29 13:52   ` T.V Raman
2018-05-29  3:10 ` Richard Stallman
2018-05-29 16:54   ` Eli Zaretskii
2018-05-29 18:02     ` George Plymale II
2018-05-30  7:04       ` Tim Cross
2018-05-30 10:53         ` Basil L. Contovounesios
2018-06-03 18:29       ` Jefferson Carpenter
2018-05-29 14:02 ` Drew Adams
2018-05-29 14:40   ` Rostislav Svoboda
2018-05-29 15:10     ` Gian Uberto Lauri
2018-05-30  7:23 ` Andreas Röhler
2018-05-30  8:15   ` Boruch Baum
2018-05-30 10:56 ` Dmitry Gutov
2018-05-31 15:59   ` Kaushal Modi
2018-05-31 22:57     ` John Yates
2018-06-01  8:09       ` Eli Zaretskii
2018-06-01  3:02     ` Richard Stallman
2018-06-01 14:02       ` John Yates
2018-06-02  3:29         ` Richard Stallman
2018-06-02 12:30           ` John Yates
2018-06-03  2:32             ` Richard Stallman
2018-06-03 14:58               ` Eli Zaretskii
2018-06-04  4:16                 ` Richard Stallman
2018-06-04  4:47                 ` Marcin Borkowski
2018-06-04  5:09                   ` Amin Bandali
2018-06-04  8:30                     ` Marcin Borkowski [this message]
2018-06-04  8:53                       ` Van L
2018-06-04 15:49                       ` Eli Zaretskii
2018-06-07 17:05                         ` Marcin Borkowski
2018-06-07 18:00                           ` João Távora
2018-06-11  3:25                             ` Marcin Borkowski
2018-06-11 13:50                               ` Joshua Branson
2018-06-12  0:35                                 ` Richard Stallman
2018-06-12  0:33                               ` Richard Stallman
2018-06-15 17:00                                 ` Marcin Borkowski
2018-06-15 17:44                                   ` Clément Pit-Claudel
2018-06-15 18:03                                     ` Marcin Borkowski
2018-06-15 18:10                                       ` João Távora
2018-06-04 23:29                       ` Richard Stallman
2018-06-07 17:06                         ` Marcin Borkowski

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87efhnar8u.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=aminb@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=kaushal.modi@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.