public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Tue, 20 Feb 2024 00:01:09 -0300	[thread overview]
Message-ID: <orle7fq1oq.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <xn34tof6x8.fsf@greed.delorie.com> (DJ Delorie's message of "Mon, 19 Feb 2024 17:03:31 -0500")

On Feb 19, 2024, DJ Delorie <dj@redhat.com> wrote:

> Alexandre Oliva <oliva@gnu.org> writes:
>> Outsourcing an individual's or a group's computing is SaaSS even when
>> using Free Software,

> You just argued that we should all stop using sourceware.org or gnu.org.

Your response just confirms that there's some misunderstanding around
the notion of SaaSS.  You may be confusing it with SaSS.

The services that gnu.org and sourceware.org offer are publishing and
communication, that are not any one party's computing, and that
necessarily involve more than one party.  These are not SaaSS.
See "Distinguishing SaaSS from Other Network Services" on
https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html

You may also get a better understanding by reading "When the User Is a
Collective Activity Or an Organization" on the same web page.  It
applies to our case.

> I respect the SaaSS argument, but we have to draw the line somewhere or
> we can't work together at all.  Trust has to be a factor.

The line is drawn, it just needs to be understood and respected.

It has enabled us to work together for a long time.  Currently, we're
not outsourcing our computing, so there's no loss of software freedom,
regardless of whom we trust.

Trust may play a role when it comes to communication and publishing
services, and we have a reasonably trusted party we've all relied on for
a long time.  There's a push to move them to a third party that is not
uniformly better trusted, which is a problem in itself.

But the anathema IMHO is that the plans AFAICT involve outsourcing our
computing.  That would be crossing a line that nobody should cross, and
we, the Free Software movement, as the reference in this issue, must be
the change we wish to see in the world, not seek ways to compromise.

-- 
Alexandre Oliva, happy hacker                    https://FSFLA.org/blogs/lxo/
   Free Software Activist                           GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice but
very few check the facts.  Think Assange & Stallman.  The empires strike back

  parent reply	other threads:[~2024-02-20  3:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` Alexandre Oliva
2023-08-30 17:31   ` Joseph Myers
2023-08-31 19:59     ` Paul Eggert
2023-09-01  6:03       ` Sam James
2023-09-01  8:55         ` Florian Weimer
2023-09-01  9:02           ` Sam James
2023-09-01  9:21             ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11:52               ` Florian Weimer
2023-09-01  9:03           ` [Action Required] glibc decision to use CTI services Andrew Pinski
2023-09-01 11:49             ` Florian Weimer
2023-09-01 13:32           ` Frank Ch. Eigler
2023-09-01 12:30         ` Siddhesh Poyarekar
2023-09-01 14:54           ` Paul Eggert
2023-09-01 16:08             ` Siddhesh Poyarekar
2023-09-01 15:01           ` Sam James
2023-09-01 16:19             ` Frank Ch. Eigler
2023-09-01 16:30             ` Siddhesh Poyarekar
2023-09-02 18:25             ` Mark Wielaard
2023-09-01  9:08       ` Mark Wielaard
2023-09-03  6:31       ` Alexandre Oliva
2023-09-27 13:49       ` Carlos O'Donell
2023-10-04  0:09         ` Paul Eggert
2023-09-01 15:09     ` Alexandre Oliva
2023-09-27 13:50     ` Carlos O'Donell
2024-02-13  0:43       ` Carlos O'Donell
2024-02-19 21:22         ` Alexandre Oliva
2024-02-19 22:03           ` DJ Delorie
2024-02-20  1:49             ` Mark Wielaard
2024-02-20  3:01             ` Alexandre Oliva [this message]
2023-08-31  8:37   ` Mark Wielaard
2023-09-01 15:08     ` Alexandre Oliva
2023-08-31 10:34   ` Florian Weimer
2023-09-04  6:09     ` Alexandre Oliva

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=orle7fq1oq.fsf@lxoliva.fsfla.org \
    --to=oliva@gnu.org \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.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).