From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: Minutes from Key Reading meeting on 2024-02-16
Date: Fri, 16 Feb 2024 12:38:20 -0500 [thread overview]
Message-ID: <7cbc3da4-e129-4922-8636-632e7c64227d@redhat.com> (raw)
Meeting notes:
~~~
* Carlos and Siddhesh were present to confirm that David Edelsohn on video was present and actually there in person.
* Konstantin from LF IT was present as well to witness the key reading.
* David Edelsohn reading the key.
* David read the following key: SHA256:zkS1TzJkFI9X8gG6h0t9DWNle6IIhVC8Z7JTrXkuf2I
* Konstantin confirmed the key matches what he copied.
* Next step is for David to email it-coreprojects-helpdesk@linuxfoundation.org with the public key.
~~~
Once David emails the public key to LF IT then he will be added
as a trusted introducer for the CTI git repo and can help add
others to the repo.
Thank you everyone!
Currently we have 4 trusted introducers for repo:
* Joseph Myers
* Siddhesh Poyarekar
* David Edelsohn (soon to be added)
* Carlos O'Donell (myself)
--
Cheers,
Carlos.
next reply other threads:[~2024-02-16 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:38 Carlos O'Donell [this message]
2024-02-16 19:24 ` Minutes from Key Reading meeting on 2024-02-16 Konstantin Ryabitsev
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=7cbc3da4-e129-4922-8636-632e7c64227d@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 NNTP newsgroup(s).