From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.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 09:46:08 -0400 [thread overview]
Message-ID: <6f6d141b-b776-8707-2c91-dc38d20aa9e1@gotplt.org> (raw)
In-Reply-To: <Yzn49Yo6UcmJidsa@wildebeest.org>
On 2022-10-02 16:47, Mark Wielaard via Overseers wrote:
>> 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.
Minutes moved here:
https://gti.gotplt.org/tac/
https://gti.gotplt.org/tac/LF%20IT%20Core%20Projects%20Services.pdf
I own gotplt.org and am happy to lend the subdomain for now to help
coordinate this because I think the LF proposal is the best long term
way forward for the GNU toolchain projects to remain competitive *and* Free.
To be clear, I don't think there are any qualms about adding a license
notice here but we'd have to agree on one. I made and shared this copy
to dispel any further false speculation of scope creep of the GTI
proposal. For any content attributable to me in the meeting minutes,
I'm happy to release it under any free license the TAC may agree on.
Sid
next prev parent reply other threads:[~2022-10-04 13:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell
2022-10-02 20:47 ` Mark Wielaard
2022-10-04 13:46 ` Siddhesh Poyarekar [this message]
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
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=6f6d141b-b776-8707-2c91-dc38d20aa9e1@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).