From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Mark Wielaard <mark@klomp.org>,
Overseers mailing list <overseers@sourceware.org>,
gcc@gcc.gnu.org, libc-alpha@sourceware.org,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Thu, 6 Oct 2022 17:37:49 -0400 [thread overview]
Message-ID: <af8748a4-445f-108b-0645-7b10864bb5e4@gotplt.org> (raw)
In-Reply-To: <20221006201256.run7acqpnjofsqfw@cgf.cx>
On 2022-10-06 16:12, Christopher Faylor via Overseers wrote:
> The silence from the proponents of this project is puzzling. I wonder
> if this means there are more non-public negotiations going on somewhere,
> leaving the community out of the loop.
The proponents of this project are members of the GNU toolchain
communities. We approached the LF with the permission of the FSF to
explore infrastructure funding solutions that would work for our
communities. The proposal has been made in response to our request, so
we need to tell them what we need and not the other way around.
Also as I responded to Mark, the technical details of the transition are
the responsibility of the GTI TAC (which you were invited to be member
of and you declined) and not the LF IT, although they'd be the ones
implementing and maintaining it.
We're at that stage at the moment where we look for consensus from the
project communities so that we understand if we can move all of
sourceware to LF IT or if we need both to coexist somehow.
Once we have a direction, we talk about what that transition would look
like and ask questions accordingly. Are there services that you
absolutely cannot move to LF IT and why? Why would you support (or
oppose) porting the wiki to something like readthedocs backed by a git repo?
I respect your outright rejection of the proposal because at least it is
clear that you don't have any stake in its fine tuning.
For everyone else, it's a proposal. If there are changes you'd like to
see in it, which will result in it being acceptable for you, please feel
free to convey that. If you think it is unnecessary for your project
and that sourceware in its current state and vision is sufficient for
your needs, please state that clearly too.
Sid
next prev parent reply other threads:[~2022-10-06 21:37 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
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 [this message]
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=af8748a4-445f-108b-0645-7b10864bb5e4@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.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).