From: Carlos O'Donell <carlos@redhat.com>
To: gti-tac@lists.linuxfoundation.org
Subject: Action: Setup working group for the GNU Toolchain proposal to migrate to LF IT managed services
Date: Fri, 11 Nov 2022 12:24:38 -0500 [thread overview]
Message-ID: <3a81d482-c952-d501-f495-485f00400e85@redhat.com> (raw)
TAC,
We discussed this proposal on the 2022-11-09 TAC meeting.
Here is the action with more details. Please review and provide comments.
I'm out for the next 2 weeks, but I wanted to start this ball rolling.
Action:
Setup a working group for the proposal to transition to LF IT managed services.
The WG is tasked by the TAC to initially enumerate in detail the GNU Toolchain
project services.
Details:
- Working group will enumerate in detail the GNU Toolchain project services
for the projects including gcc, glibc, binutils and gdb.
- Working group will commit documents to the GTI TAC sphinx git repo with
all of the enumerated service details.
- Working group will nominate a rep to report at GTI TAC meetings on the
current status of the working group.
- GTI TAC and WG must determine next step after enumeration is complete.
Next step:
- Seek volunteers. Please respond to this email if you want to volunteer
to be on the "LF IT managed services" working group and help enumerate
services.
--
Cheers,
Carlos.
next reply other threads:[~2022-11-11 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:24 Carlos O'Donell [this message]
2022-11-11 23:36 ` Action: Setup working group for the GNU Toolchain proposal to migrate to LF IT managed services Joseph Myers
2022-11-15 19:42 ` Carlos O'Donell
2022-11-15 20:25 ` Joel Brobecker
2022-11-17 14:10 ` Simon Marchi
2022-11-21 3:31 ` Joel Brobecker
2022-11-21 3:32 ` Joel Brobecker
2022-11-21 20:49 ` Joseph Myers
2022-12-05 17:45 ` David Edelsohn
2022-12-12 4:44 ` Joel Brobecker
2022-12-06 15:52 ` Simon Marchi
2022-12-06 17:42 ` Simon Marchi
2022-12-06 17:43 ` David Edelsohn
2022-12-24 5:31 ` Joel Brobecker
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=3a81d482-c952-d501-f495-485f00400e85@redhat.com \
--to=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.