public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "Carlos O'Donell" <carlos@redhat.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: Fri, 01 Sep 2023 12:09:18 -0300	[thread overview]
Message-ID: <ora5u6hqw1.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <cc4f81c9-29b7-76af-b188-a6db4f32bcb@codesourcery.com> (Joseph Myers's message of "Wed, 30 Aug 2023 17:31:13 +0000")

On Aug 30, 2023, Joseph Myers <joseph@codesourcery.com> wrote:

> On Wed, 30 Aug 2023, Alexandre Oliva wrote:
>> 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.

> I believe the LF has already agreed to implement the hosting entirely with 
> free software.

Meeting basic requirements that, if not met, would make the service
provider profoundly hostile to software freedom is a far cry from being
in line with the movement's values.

Are you familiar with the notion of SaaSS, Service as a Software
Substitute?

"LF has agreed to such and such" doesn't sound good for me.  "We the
community have decided to implement our own services so and so" would
have made a lot of difference in avoiding the ills of SaaSS, but that
doesn't seem to even be in the radar of the path that is being proposed.

Now, this doesn't pertain to activities of publishing source code;
publishing is not SaaSS.  Remote merging, building, testing, and other
activities that are being bundled with source code publishing services,
however, are computing, community computing, and communities of such key
projects ought to not only be careful to avoid enabling third parties to
subjugate us through SaaSS, but also show other communities how to go
about avoiding that.

-- 
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:[~2023-09-01 17:15 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 [this message]
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=ora5u6hqw1.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).