From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: Share status update to OpenSSF TAC on Tuesday August 22nd at 11am ET.
Date: Wed, 16 Aug 2023 09:35:31 -0400 [thread overview]
Message-ID: <e6560aab-5f01-b8f8-0e37-ea9bfe8b6951@redhat.com> (raw)
CTI TAC,
In 2023 we have several opportunities to share GTI TAC status to the
OpenSSF TAC. The OpenSSF TAC has representatives industry wide.
The next presentation slot for CTI is on Tuesday August 22nd at 11am EDT.
It's a short 10 minute slot.
I think this is a great opportunity to share status and get feedback
from the broader OpenSSF community.
Presenting status breaks down into the following steps:
- Summarize progress to date.
- Write down any open questions we might have.
- Present progress to the OpenSSF TAC.
- Ask for feedback on anything we think would be useful or valuable.
I would be happy to work with someone to wordsmith a high-level update.
Would anyone like to volunteer to write up a summary to date?
Would anyone like to present to the OpenSSF TAC?
The next presentation is November 14th, 2023, and I'll send another
"share status" email as we approach that date.
--
Cheers,
Carlos.
reply other threads:[~2023-08-16 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e6560aab-5f01-b8f8-0e37-ea9bfe8b6951@redhat.com \
--to=carlos@redhat.com \
--cc=cti-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).