public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
	gdb@sourceware.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Tue, 4 Oct 2022 21:05:27 +0200	[thread overview]
Message-ID: <YzyD9wWLVexFZA+L@wildebeest.org> (raw)
In-Reply-To: <05b0f7fa-7077-5a8b-0c2f-dfb3068dd10f@gotplt.org>

Hi Siddhesh,

On Tue, Oct 04, 2022 at 01:17:14PM -0400, Siddhesh Poyarekar wrote:
> On 2022-10-04 13:10, Christopher Faylor wrote:
> > On Tue, Oct 04, 2022 at 09:46:08AM -0400, Siddhesh Poyarekar wrote:
> > > I made and shared this copy to dispel any further false speculation of
> > > scope creep of the GTI proposal.
> > 
> > Who is doing the false speculation?  Do you have a mailing list link?
> > It would be interesting to know who's got it wrong.
> 
> Mark asked upthread if content on gnu.org is also going to be migrated over

I did indeed. Both the proposal and these minutes mention migrating
websites without mentioning any specifics. Knowing which websites are
meant and why they need migration is useful information.

The FSF tech team is helping us coordinating things on overseers to
help with release archives, mirroring, backups and sourceware
continuity. If this is about migrating websites currently on
www.gnu.org then talking to the FSF tech team does make sense. If it
isn't about that, then we will simply note that and move one.

We do take this proposal, and all other suggestions people make about
the sourceware infrastructure, seriously, but a lot of details of this
proposal are still unclear. We are trying to get as much details as
possible so we can see how this fits into the current sourceware
roadmap, get a better understanding of the budgetary needs, file
sourceware infrastructure bugs with those details. All to get a better
understanding what the real needs are and document the necessary steps
forward.

Cheers,

Mark

  parent reply	other threads:[~2022-10-04 19:05 UTC|newest]

Thread overview: 41+ 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 [this message]
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
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
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
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell

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=YzyD9wWLVexFZA+L@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 \
    --cc=siddhesh@gotplt.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).