From: Carlos O'Donell <carlos@redhat.com>
To: Adrianne Marcum <amarcum@linuxfoundation.org>
Cc: Bennett Pursell <bpursell@linuxfoundation.org>,
cti-tac@lists.linuxfoundation.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Setting up an LF IT meeting to kick off the glibc service migration plan design and SOW.
Date: Thu, 28 Mar 2024 13:19:56 -0400 [thread overview]
Message-ID: <be7265ce-3df9-43db-a217-5a036f717382@redhat.com> (raw)
Adrianne,
Here is the list of invites for the LF IT discussion about the
service migration plan design and SOW.
Thank you for your help in setting up the invitations and organizing.
We should use BBB for the meeting:
https://bbb.linuxfoundation.org/room/adm-iuc-px7-mk1
CTI TAC:
Joseph Myers <joseph@codesourcery.com>
Carlos O'Donell <carlos@redhat.com>
Siddhesh Poyarekar <siddhesh@redhat.com>
David Edelsohn <dje.gcc@gmail.com>
LF IT:
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
(or LF IT delegates that Konstantin suggests)
Optional CTI TAC (optional because they aren't directly involved in glibc):
Joel Brobecker <brobecker@adacore.com>
Jose Marchesi <jose.marchesi@oracle.com>
Simon Marchi <simon.marchi@efficios.com>
Frank Ch. Eigler <fche@redhat.com>
Nick Clifton <nickc@redhat.com>
Jeff Law <jeffreyalaw@gmail.com>
Optional FSF (optional if Ian has time):
Ian Kelling <iank@fsf.org>
Everyone will get to see the migration plan and SOW as we prepare it,
but I'd like a kick-off meeting to sketch out the plan in person.
--
Cheers,
Carlos.
next reply other threads:[~2024-03-28 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 17:19 Carlos O'Donell [this message]
[not found] ` <CAGWvnykD2tjWhvzT0S_62daU__w3Fa54AzRoZfCffzz7d5qTkg@mail.gmail.com>
2024-03-28 22:43 ` Setting up an LF IT meeting to kick off the glibc service migration plan design and SOW 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=be7265ce-3df9-43db-a217-5a036f717382@redhat.com \
--to=carlos@redhat.com \
--cc=amarcum@linuxfoundation.org \
--cc=bpursell@linuxfoundation.org \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=konstantin@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 read-only IMAP folder(s) and NNTP newsgroup(s).