Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Free as in Freedom - a response to the latest discussion in our support chat
Date: Thu, 9 Apr 2026 20:00:04 +0200	[thread overview]
Message-ID: <CAJUtOOgA2NfxXznb3a1Nrxd3BUx+jj0gxBHHryut2aqUc7WqrA@mail.gmail.com> (raw)

Hello to all,

We have decided to write this blog post as a longer response addressing
latest discussion in our support chat re: LibreQoS pricing:


*https://devblog.libreqos.com/posts/0015-free-as-in-freedom/
<https://devblog.libreqos.com/posts/0015-free-as-in-freedom/>*

English really is a wretched language in some ways. “Free” can mean
“Freedom” and can mean “Without Charge”. The French have a much better
system, with “libre” (free as in freedom) and “livre” (free as in free
beer) being separate words. That’s led to decades of confusion and debate -
but ultimately, I think we can defer to Richard Stallman (founder of GNU
and the GPL) for a definition:

“When we speak of free software, we are referring to freedom, not price,”
> advised Stallman in the GPL’s preamble. By the late 1980s, Stallman had
> refined it to a more simple mnemonic: “Don’t think free as in free beer;
> think free as in free speech.” (1 - page 132)


If you dig into Stallman’s writings (I highly recommend it), you’ll see
that he’s addressed this time and time again. He’s even said that
dual-licensing is fine, GPL software can carry a price (it’s free so long
as the source remains free - you can charge for access to the software;
otherwise, Red Hat wouldn’t have been able to succeed).


All the best,

Frank

Frantisek (Frank) Borsik


*In loving memory of Dave Täht: *1965-2025

https://libreqos.io/2025/04/01/in-loving-memory-of-dave/


https://www.linkedin.com/in/frantisekborsik

Signal, Telegram, WhatsApp: +421919416714

iMessage, mobile: +420775230885

Skype: casioa5302ca

frantisek.borsik@gmail.com

                 reply	other threads:[~2026-04-09 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAJUtOOgA2NfxXznb3a1Nrxd3BUx+jj0gxBHHryut2aqUc7WqrA@mail.gmail.com \
    --to=frantisek.borsik@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /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