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: Joseph Myers <joseph@codesourcery.com>,
	"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>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Wed, 30 Aug 2023 14:19:20 -0300	[thread overview]
Message-ID: <orsf805tyf.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com> (Carlos O'Donell's message of "Tue, 29 Aug 2023 18:02:22 -0400")

[adding libc-alpha, where GNU libc discussions are held]

On Aug 29, 2023, "Carlos O'Donell" <carlos@redhat.com> wrote:

> I propose the glibc project migrate to services provided by the 
> Core Toolchain Infrastructure (CTI) project, particularly services
> provided by the Linux Foundation IT team.

Nay.  I do not perceive any benefits to GNU's values in becoming
technologically dependent on an organization that never shared GNU's
values, that has constantly pretended GNU didn't exist, persistently
claimed our work to itself, and promotes and operates under values that
conflict deeply with those that GNU stands for.  It would amount to
shooting itself in the paws.

I acknowledge that the present supplier of equivalent services also
started in a hostile manner, but at this point it's the devil we know.

The plan should IMHO be to mitigate that dependency, not introduce
another or replace one with a worse one.

As I suggested back when this idea was first raised (and AFAICT there
have been no attempts to dispute that this would be a better path to
pursue), I'd be happy to accept this sort of contribution to GNU *iff*
the services were *actively* *replicated* among two or three separate
suppliers, so as to reduce the risk of dependency and of corrupting
pressure on us.

Even then, this would IMHO be a move for GNU to decide, or at the very
least be consulted on, according to its own values and priorities,
something that all mantainers appointed by GNU, myself included,
committed ourselves to observe, prioritize and uphold as maintainers of
GNU packages.  I encourage other maintainers to justify their responses
based on GNU's values and priorities, as they understand them.

-- 
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:[~2023-08-30 17:19 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 [this message]
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
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=orsf805tyf.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).