From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: CTI TAC Meeting Notes 2023-06-28
Date: Wed, 28 Jun 2023 12:02:43 -0400 [thread overview]
Message-ID: <7d4d9764-dfc0-a0b8-c5f0-010305e70995@redhat.com> (raw)
CTI TAC Meeting Notes 2023-06-28
Present TAC members:
- Joseph Myers
- David Edelsohn
- Siddhesh Poyarekar
- Carlos O'Donell
Present community members:
- Ian Kelling (unable to sign in to BBB)
Agenda:
- Status of update to the glibc community.
- Carlos will talk about current status and writeup.
- Not yet sent to libc-alpha, but plan to finish this week.
- Discussed the key points for the outbound communication from TAC to glibc community.
- Clarify next steps are that Stewards need to review and decide.
- Clarify that it is LF IT that would be providing the services.
- David: tl;dr put the justification at the top (moved from the bottom)
- Provide a stronger executive summary at the top.
- "This is the proposed plan to move forward"
- "Use the knowledge and skills of the entire community to review service requirements"
- Make a clear statement that we would like to move forward.
- Add grounding paragraph at the top for the structure of the email.
- Action item: Carlos to mail out update to glibc community.
- Space for CTI TAC documents.
- Should we have a web presence to put up documents?
- Carlos: Yes, to upload videos and tac notes.
- Siddhesh: Yes.
- Joseph: Yes.
- David: Yes.
- May we use "toolchain.dev" ? - David: Yes.
- Siddhesh: We should have git repo, with a web site e.g. LF IT rst/sphinx website.
- Siddhesh: Does LF have a Gitlab instance for doing this?
- Action item: Carlos to email LF IT on CTI TAC list to answer question about gitlab instances.
- Noted that Ian Kelling could not sign in from remote location and will follow up with BBB admins to discuss possible routing issues.
- David: Preliminary budget estimates are difficult for LF IT to come up with. Continued discussing with LF IT and OpenSSF CTO to determine costs and continue to seek out additional direct sponsors.
--
Cheers,
Carlos.
reply other threads:[~2023-06-28 16:03 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=7d4d9764-dfc0-a0b8-c5f0-010305e70995@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).