From: Carlos O'Donell <carlos@redhat.com>
To: gti-tac@lists.linuxfoundation.org
Subject: Planning the next GTI TAC meeting.
Date: Tue, 1 Nov 2022 17:41:04 -0400 [thread overview]
Message-ID: <b246cbec-4c4e-940f-2b47-5e2f9f721adc@redhat.com> (raw)
TAC,
We're trying to get a BBB instance setup so the next meeting of the
GTI TAC is using entirely FOSS. So this meeting may need to move out
as we discuss the use of conferencing technology and how to attend
and record the meeting.
Please look at your calendar and get back to me about the following dates:
* Tuesday November 8th at 11am EST5EDT
* Wednesday November 9th at 10am EST5EDT
* Friday November 11th at 9am EST5EDT
The agenda for the GTI TAC meeting would be to discuss the next steps
for the current proposal: the GNU Toolchain moving to managed
infrastructure at the LF IT. We could additionally discuss some of
the mechanics of the TAC, like where we'll put our documents, notes
and recordings (I have some ideas on that).
Thank you!
--
Cheers,
Carlos.
next reply other threads:[~2022-11-01 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 21:41 Carlos O'Donell [this message]
2022-11-07 2:12 ` Planning the next GTI TAC meeting 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=b246cbec-4c4e-940f-2b47-5e2f9f721adc@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 read-only IMAP folder(s) and NNTP newsgroup(s).