GTI TAC Meeting Notes 2023-06-08

GTI TAC Meeting Notes 2023-06-08

[Carlos O'Donell]

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.

Re: GTI TAC Meeting Notes 2023-06-08

[Konstantin Ryabitsev]

On Wed, Mar 08, 2023 at 11:44:47AM -0500, Carlos O'Donell wrote:
> - Carlos: Where does the complexity come from?
> - Jeff: Mailing list from bugzilla integration. Lots of custom stuff.

Can someone pass me the details of this integration? I'm currently working on
bugzilla mailing list integration via lore.kernel.org and I can see if this is
something I'm already handling.

-K

Re: GTI TAC Meeting Notes 2023-06-08

[Carlos O'Donell]

On 3/8/23 14:29, Konstantin Ryabitsev wrote:
> On Wed, Mar 08, 2023 at 11:44:47AM -0500, Carlos O'Donell wrote:
>> - Carlos: Where does the complexity come from?
>> - Jeff: Mailing list from bugzilla integration. Lots of custom stuff.
> 
> Can someone pass me the details of this integration? I'm currently working on
> bugzilla mailing list integration via lore.kernel.org and I can see if this is
> something I'm already handling.

We haven't finished the gcc service enumeration yet, it's the last project remaining.

We will dig into this and provide you with the details as part of that enumeration.

Off the top of my head:

Normal Bugzilla behaviour:
- Bugzilla issue updates go to the mailing list.
- Email responses to the mailing list messages go back to the referenced bug.

Customization:
- gcc refs/meta/config project.config used to store customization data.
- git commit hooks used to:
  - Send email to mailing list.
  - Update bugzilla if issues referenced in commit.
    e.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109062#c1

The gcc project itself has ~6k lines of python in the git commit
hooks and part of that handles "message" customization.

-- 
Cheers,
Carlos.

Re: GTI TAC Meeting Notes 2023-06-08

[Martin Liška]

On 3/10/23 05:50, Carlos O'Donell wrote:
> The gcc project itself has ~6k lines of python in the git commit
> hooks and part of that handles "message" customization.

Hi.

Do you mean the copy of contrib/gcc-changelog where we verify the ChangeLog format?
Note it's just of copy of what we have in the main repo:
https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=contrib/gcc-changelog;h=1978dc6e4f6572e88b27898a9abe849d7ccdb883;hb=HEAD

Cheers,
Martin