From: Carlos O'Donell <carlos@redhat.com>
To: gti-tac@lists.linuxfoundation.org
Subject: Planning the next GTI TAC meeting for March 8th.
Date: Wed, 1 Mar 2023 10:16:57 -0500 [thread overview]
Message-ID: <db67f1f9-320c-18fc-f196-5923cc622c0a@redhat.com> (raw)
Team,
I would like to setup a GTI TAC meeting for March 8th at 11am EST / 4pm GMT.
Does that work?
Agenda:
- Pick a time for regular monthly meetings.
- glibc: Next steps for glibc, and the process for migrating a whole
project to LF infrastructure
- Going to the LF IT core projects team and asking for review of
glibc services and cost.
- Approval from GTI.
- Community discussion.
- GNU Maintainer decision.
- Setting up gti.toolchain.dev to hold documents and notes from the
meetings?
Please add your agenda items.
--
Cheers,
Carlos.
next reply other threads:[~2023-03-01 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:16 Carlos O'Donell [this message]
2023-03-02 16:42 ` Planning the next GTI TAC meeting for March 8th Simon Marchi
[not found] ` <87356l7tix.fsf@gnu.org>
2023-03-07 4:17 ` Carlos O'Donell
[not found] ` <87bkkajo24.fsf@gnu.org>
2023-03-30 15:06 ` 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=db67f1f9-320c-18fc-f196-5923cc622c0a@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 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 NNTP newsgroup(s).