public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: libc-alpha@sourceware.org, binutils@sourceware.org,
	gdb@sourceware.org, gcc@gcc.gnu.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Sun, 2 Oct 2022 22:47:49 +0200	[thread overview]
Message-ID: <Yzn49Yo6UcmJidsa@wildebeest.org> (raw)
In-Reply-To: <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>

Hi,

We are using overseers to coordinate this and see how we can
mix-and-match pieces of this proposal. And to better understand how
this proposal interacts with Sourceware becoming a Conservancy member
project. So I added overseers@sourceware.org to have one central place
for these discussions.

On Wed, Sep 28, 2022 at 06:38:02PM -0400, Carlos O'Donell via Libc-alpha wrote:
> On 9/27/22 16:08, Carlos O'Donell wrote:
> > "The GNU Toolchain Infrastructure Project"
> > https://sourceware.org/pipermail/overseers/2022q3/018896.html
> 
> I've published the current GTI TAC meeting minutes to the glibc website:
> https://www.gnu.org/software/libc/gti-tac/index.html
> 
> The slides from the LF IT are a good overview:
> https://www.gnu.org/software/libc/gti-tac/LF%20IT%20Core%20Projects%20Services.pdf

I assume www.gnu.org was the easiest way for you to quickly make these
things public. But it now does look like it is an official FSF/GNU
proposal. Which I assume wasn't your intention. Note that it contains
a copyright notice "© 2022, GTI TAC." but doesn't seem to have a
(free) license. Which is kind of necessary if you host it on
www.gnu.org.

This does raise the question if you are also proposing migrating
non-sourceware services for projects like the websites of various of
the GNU projects on www.gnu.org or the release archives at the GNU ftp
server (and mirrors) those projects use.

The attendees list a subset of the GTI TAC members you posted
earlier. Was there any other way for people to participate in these
discussions? Did the GTI TAC invite the LF/IT team to give this
presentation or was this a proposal from the LF?

I note that this discussion and what you presented at Caudron was for
the migration of all services of all projects hosted on
Sourceware. But that your latest proposal is just for a subset of
projects, possibly only in part as would best suit their needs.

Lets file some sourceware infrastructure bugzilla entries for some of
these ideas in this presentation, to get a better understanding what
the real needs are. It would also be nice to hear the prices/budget
for the various options suggested in the presentation.

Cheers,

Mark

       reply	other threads:[~2022-10-02 20:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
     [not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47   ` Mark Wielaard [this message]
2022-10-04 13:46     ` Siddhesh Poyarekar
2022-10-04 14:01       ` Frank Ch. Eigler
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler
2022-10-06 21:42             ` Alexandre Oliva
2022-10-04 17:10       ` Christopher Faylor
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor
2022-10-04 19:05           ` Mark Wielaard
2022-10-04 19:10             ` Siddhesh Poyarekar
2022-10-06 20:02               ` Mark Wielaard
2022-10-06 20:12                 ` Christopher Faylor
2022-10-06 21:37                   ` Siddhesh Poyarekar
2022-10-07 13:39                     ` Mark Wielaard
2022-10-06 21:07                 ` Siddhesh Poyarekar
2022-10-06 21:36                   ` Frank Ch. Eigler
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler
2022-10-11 13:02                         ` Siddhesh Poyarekar
2022-10-07  8:57                   ` Mark Wielaard
2022-10-11 13:24                     ` Siddhesh Poyarekar
2022-10-11 14:23                       ` Frank Ch. Eigler
2022-10-11 15:58                     ` Alexandre Oliva
2022-10-11 17:14                       ` David Edelsohn
2022-10-11 18:12                         ` Frank Ch. Eigler
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell
2022-09-29 10:02 ` Nick Clifton
2022-10-02 20:54   ` Mark Wielaard
2022-10-03 19:24   ` Carlos O'Donell
2022-10-17 11:48   ` Luis Machado
2022-10-17 12:08     ` Siddhesh Poyarekar
2022-10-17 12:16       ` Luis Machado
2022-10-18 18:45         ` Siddhesh Poyarekar

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=Yzn49Yo6UcmJidsa@wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=overseers@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).