LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "J.B. Nicholson" <jbn@forestfield.org>
To: libreplanet-discuss@libreplanet.org
Subject: What will we do without Richard Stallman? Push for more software freedom as per usual.
Date: Tue, 17 Sep 2019 18:14:17 -0500	[thread overview]
Message-ID: <9c8d4e1c-dc9b-92e2-8470-176e3e3d1dc7@forestfield.org> (raw)
In-Reply-To: <e7d3d9a3-a928-bfbd-a7a9-0ca0c9b15a4d@yahoo.com>

fudmier via libreplanet-discuss wrote:
> Forcing human rights and democracy first Icon Stallman to resign..seems
> to suggest a bigger plan with roots in a design that has as its object
> to deny to the world the open source developer invented products and
> instructional expertise.
It would be better not to conflate Stallman or his work with "open source". 
As he (and history) have made clear: he founded the free software movement 
(a social movement) over a decade before "open source" (a development 
methodology). He has mentioned in multiple interviews, articles, and 
virtually every speech I've ever heard him give (including almost all on 
https://audio-video.gnu.org/) that he does not stand for open source but 
for free software. I trust the readership of this mailing list doesn't need 
anyone to recite a long list of links to this end. For anyone new to free 
software: welcome and please do read the essays on 
https://www.gnu.org/philosophy/ because the issues discussed therein are 
still apropos to the FSF's central mission and what we mainly talk about on 
this mailing list.

> Gee, what will we do without Richard Stallman?

You might not have intended it this way, but I hope that this question is 
taken with utmost seriousness. Fortunately for us he's not dead; RMS can 
continue to publish informative, insightful essays & talks on his own. However:

1. RMS is mortal and (like us all) will someday die,
2. the FSF has begun a search for a new president. (per 
https://www.fsf.org/news/richard-m-stallman-resigns),

Because of these things there is a chance someone will become the next FSF 
president who isn't the sharp defender of software freedom RMS has always been.

It would be a shame if the FSF made a compromise where they favored sating 
a desire for identity politics, say, and occasionally gave into proprietor 
pressure groups or ran proprietary software over someone who consistently 
demonstrated unyielding support for software freedom. I hope they'll pick 
someone who is deeply informed about free software, and who possesses a 
sharp, critical stance in defense of software freedom. The mission of the 
FSF doesn't change just because they get a new president.

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2019-09-17 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.95.1568736033.31266.libreplanet-discuss@libreplanet.org>
2019-09-17 17:59 ` libreplanet-discuss Digest, Vol 113, Issue 15 fudmier via libreplanet-discuss
2019-09-17 23:14   ` J.B. Nicholson [this message]
2019-09-20 20:29     ` FSF has begun a search for a new president Dmitry Alexandrov
2019-09-21 22:36       ` Leah Rowe via libreplanet-discuss

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=9c8d4e1c-dc9b-92e2-8470-176e3e3d1dc7@forestfield.org \
    --to=jbn@forestfield.org \
    --cc=libreplanet-discuss@libreplanet.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.
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).