public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: DJ Delorie <dj@redhat.com>
Cc: Alexandre Oliva <oliva@gnu.org>, libc-alpha@sourceware.org
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Tue, 20 Feb 2024 02:49:22 +0100	[thread overview]
Message-ID: <20240220014922.GK16832@gnu.wildebeest.org> (raw)
In-Reply-To: <xn34tof6x8.fsf@greed.delorie.com>

Hi,

On Mon, Feb 19, 2024 at 05:03:31PM -0500, DJ Delorie 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.
> 
> 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.

I do hope the glibc community trusts Sourceware.

The Sourceware Project Leadership Committee does have regular
discussions with the FSF and coordinates with the FSF tech-team around
shared services we provide to GNU projects like glibc.

Also we made sure that in our agreement with our fiscal sponsor, the
Software Freedom Conservancy, we put in writing that any
infrastructure software used is and will be published as Free
Software. See the Fiscal Sponsorship Agreement at
https://sourceware.org/mission.html#plc

If the glibc community has any concerns about the Sourceware
infrastructure and services, or simply would like to improve them,
then please do reach out:
https://sourceware.org/mission.html#organization

The Sourceware Project Leadership Committee also meets once a month to
discuss all community input, set priorities and decide how to spend
funds, etc.

Cheers,

Mark

  reply	other threads:[~2024-02-20  1:49 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 [this message]
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=20240220014922.GK16832@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=oliva@gnu.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).