CTI Technical Advisory Committee
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <josmyers@redhat.com>,
	Siddhesh Poyarekar <siddhesh@redhat.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	Nick Clifton <nickc@redhat.com>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Please review content for cti.coretoolchain.dev.
Date: Wed, 28 Feb 2024 18:35:58 -0500	[thread overview]
Message-ID: <67e9372d-9fe8-4a81-b43b-db69ed3c2b06@redhat.com> (raw)

Joseph, Siddhesh, David, Nick,

Thank you for agreeing to look over the content.

Please provide feedback on structure and content.

To review the built website you can do:

$ git clone gitolite.coretoolchain.dev:cti/cti.coretoolchain.dev

Then you can build the website with:

$ make html

You can also check spelling with `make spelling` (requires installed
sphinxcontrib-spelling, which on Fedora is as straight forward as
`sudo dnf install python3-sphinxcontrib-spelling`).

Nick,

Please send me the pub key part of the ssh key you want to use to
access the repository?

My next steps with Nick will be:
- Face to face meeting where Nick reads his key to me.
- I will then add the key to the CTI keyring and sign that commit.
- I will then work with LF IT to give Nick access to gitolite
  and write down the procedure in more detail.

My thoughts on this topic are that only one trusted introducer is
required to grant a user access to the repo, but this should not
confer trusted introducer status (I'm using Nick as a test subject
for this process).

-- 
Cheers,
Carlos.


                 reply	other threads:[~2024-02-28 23:36 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=67e9372d-9fe8-4a81-b43b-db69ed3c2b06@redhat.com \
    --to=carlos@redhat.com \
    --cc=cti-tac@lists.linuxfoundation.org \
    --cc=dje.gcc@gmail.com \
    --cc=josmyers@redhat.com \
    --cc=nickc@redhat.com \
    --cc=siddhesh@redhat.com \
    /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).