public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: "Ryan S. Arnold" <ryan.arnold@gmail.com>,
	Paul Eggert <eggert@cs.ucla.edu>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	Jakub Jelinek <jakub@redhat.com>, Andreas Schwab <schwab@suse.de>,
	libc-alpha <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Mon, 19 Feb 2024 18:22:50 -0300	[thread overview]
Message-ID: <orsf1op2s5.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <fe18e23a-1030-4a5a-8279-3280a0d7076f@redhat.com> (Carlos O'Donell's message of "Mon, 12 Feb 2024 19:43:14 -0500")

On Feb 12, 2024, "Carlos O'Donell" <carlos@redhat.com> wrote:

> On 9/27/23 09:50, Carlos O'Donell wrote:
>> I agree completely with Joseph here that the repo criteria [1] are the relevant
>> criteria to apply in this case.

> We believe that we are satisfying all of the requirements that the FSF
> and the GNU Project are requiring. Do you wish to raise any other FSF
> or GNU Project requirements?

I don't speak for the FSF or for GNU, and I'm not a party to any of the
agreements you may have made with them, but I'd be surprised if the
requirements were indeed satisfied.

Outsourcing an individual's or a group's computing is SaaSS even when
using Free Software, and SaaSS triggers basically the same obstacles to
users' freedom that nonfree software does, but in a way that makes users
even more helpless, so our movement rules out both SaaSS and nonfree
software.

From what I know of the FSF and of the GNU project, they surely wouldn't
be on board with that sort of outsourcing, and AFAICT that sort of
outsourcing is precisely what's being proposed, so I recommend you check
back with them.

When you do, I suspect you'll find that your belief arises out of some
sort of misunderstanding as to the requirements.

-- 
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

  reply	other threads:[~2024-02-19 21:23 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 [this message]
2024-02-19 22:03           ` DJ Delorie
2024-02-20  1:49             ` Mark Wielaard
2024-02-20  3:01             ` Alexandre Oliva
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=orsf1op2s5.fsf@lxoliva.fsfla.org \
    --to=oliva@gnu.org \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=ryan.arnold@gmail.com \
    --cc=schwab@suse.de \
    /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).