cti-tac.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: First round of feedback incorporated into https://cti.coretoolchain.dev/
Date: Fri, 8 Mar 2024 17:53:26 -0500	[thread overview]
Message-ID: <9451ae83-0cf9-4e1d-8408-f2c9acb46586@redhat.com> (raw)

TAC,

I've completed the first round of edits given feedback from the CTI TAC
and I'll be passing the live site URL to Paul Eggert and the glibc
stewards for review. This is to meet my March 8th deadline for moving
this forward with the glibc stewards.

Siddhesh,

Thank you for all of your cleanups and feedback, as far as I can tell
your feedback has been incorporated by yourself. We coordinated this
via the list and reviewed the content.

David,

Thank you for your feedback on the site structure. I've incorporated
as much as I could right now and I think the site is much better
because of your suggestions. Please have another look. There are still
good suggestions from you that I need to review and consider, but I
time boxed what I could do.

Joseph,

Please feel free to provide any feedback. I don't have any from you
yet.

Nick,

Given my schedule I haven't had a chance to get you authenticated
access to the repository, but we've solved that by getting read-only
anonymous access in place:
https://git.coretoolchain.dev/

-- 
Cheers,
Carlos.

Note: Graphics are drawn by myself and so we have no license issues
with them, but they are just temporary place holders. We can replace
them at any time. I was aiming for something like what PSF has:
https://www.python.org/psf-landing/


                 reply	other threads:[~2024-03-08 22:53 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=9451ae83-0cf9-4e1d-8408-f2c9acb46586@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).