gti-tac.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: gti-tac@lists.linuxfoundation.org
Subject: GTI TAC Meeting Notes 2023-06-08
Date: Wed, 8 Mar 2023 11:44:47 -0500	[thread overview]
Message-ID: <b72a0c4f-fed3-7418-e9d6-7a277bf37b3e@redhat.com> (raw)

Agenda: 
- Pick a time for regular monthly meetings.
- glibc: Next steps for glibc, and the process for migrating a whole project to LF infrastructure  
- Going to the LF IT core projects team and asking for review of glibc services and cost.  
- Approval from GTI.  
- Community discussion.  
- GNU Maintainer decision.
- Setting up gti.toolchain.dev to hold documents and notes from the  meetings?

2023-06-08:
- Welcome to Khahil White (Linux Foundation Program Manager on OpenSSF and AlphaOmega)
- Welcome to David Wheeler (Linux Foundation)
- Current status is 3/4 projects have detailed service enumeration complete.
- Gcc still missing for service enumeration.
- Carlos: I'll reach out to Joseph again about gcc service enumeration.
- David: GCC by far is likely the most complicated.
- Carlos: Where does the complexity come from?
- Jeff: Mailing list from bugzilla integration. Lots of custom stuff.
- Suggestion from Carlos to the GTI TAC - Run through glibc from start to finish.
- Carlos: Working through one project as a first target.
- Simon: Bringing binutils probably means bringing gdb.
- Jeff: Yes, they share a repo.
- Joseph: Seems reasonable as a project to start with.
- Siddhesh: Buildbot repository not in use anymore.
- Migrating glibc seems like a good first project.
- David: Make it clear with the OpenSSF that scaling up is not going to be 4x the cost because services are going to be shared.
- Asked Khahil White if this works for the OpenSSF, that we don't want to scare anyone into thinking this is 4x the cost.
- Joseph: I still intend to work on it, but I need to get time for that.
- Joseph: Do we want read-only access to old rcs/cvs?
- Joseph: Anonymous rsync?
- AI: Carlos to review existing glibc rcs/cvs/rsync and shut down those services.
- Joseph: Migrate services vs. bugzilla (two of them, gcc + classpath, the other has loads of stuff).
- Next Steps:
     - One last pass over glibc services with an eye towards adding legacy services that will be shutdown.
     - Take the glibc services list to LF IT core Project for pricing and explain that we want to tackle this on a project-by-project basis.
     - Ask LF IT to setup gti.toolchain.dev for use to store docs and minutes presentation.

-- 
Cheers,
Carlos.


             reply	other threads:[~2023-03-08 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 16:44 Carlos O'Donell [this message]
2023-03-08 19:29 ` GTI TAC Meeting Notes 2023-06-08 Konstantin Ryabitsev
2023-03-10  4:50   ` Carlos O'Donell
2023-03-10  8:01     ` Martin Liška

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=b72a0c4f-fed3-7418-e9d6-7a277bf37b3e@redhat.com \
    --to=carlos@redhat.com \
    --cc=gti-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).