11 Aug 2025 - GitProxy Meeting Minutes #1148
Description
Date
20250811 - time
Meeting info
Untracked attendees
- Full Name, Affiliation, (optional) GitHub username
- ...
Meeting notices
-
FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
-
All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
-
FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
-
FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
Agenda
- Convene & roll call (5mins)
- Display FINOS Antitrust Policy summary slide
- Review Meeting Notices (see above)
- Approve past meeting minutes
- New maintainers, onboarding, duties (review, releases, meetings etc.)
- Remaining work on feat(key on repo url): support git hosts other than GitHub + multiple forks #1043
- Roadmap Roadmap - GitProxy v2 and beyond! #1119
Minutes
- New maintainers, onboarding, duties (review, releases, meetings etc.)
- A further 2 maintainers were appointed since the last meeting (@06kellyjac & @kriswest) - @06kellyjac has been involved with the project for sometime, @kriswest for the past few months.
- @kriswest asked: What processes do we need to understand and what duties do we need to take on as Git proxy maintainers?
- Noting that projects with multiple maintainers operating release and other key workflows are less at risk/more resilient
- @jescalada commented that most workflows for git proxy are automated
- The release workflow is triggered by tagging a release
- Github suggests an overview for the release, which is then edited in the github UI and improved if necessary.
- The 2.0 release will need more than the auto-generated summary
- None of the maintainers present were sure what triggers documentation releases...
- The release workflow is triggered by tagging a release
- Renovate,js
- Raises PRs periodically... some of the open RPs are from renovate. @kriswest is unsure how to interact with those currently.
- Reviewing
- @jescalada has been jumping on most PRs for the initial review (which is much appreciated by all)
- @06kellyjac is helping out where he can, has been busy later, but is freeing up and should be able to help.
- @kriswest will start trying to help out, has previously commented on a few of the PRs
- @kriswest floated the idea of using more labelling of issues and PRs (project infrastructure, tech debt, roadmap commitment etc.)
- @jescalada commented that we have 37 open PRs, 15 of which are active, the rest are either from renovate or stale.
- There was consensus that reducing the set of open issues and PRs would be good for the project.
- @robmoffat checked in on behalf of FINOS on the project participants, now that the security disclosures and remediation PRs have been unblocked and merged and new maintainers appointed, how is the project doing.
- There was consensus that the new maintainer appointments have/will help, but that recruiting more participants would strengthen the project further.
- @tabathad provided the LF insights for the project: https://insights.linuxfoundation.org/project/git-proxy/contributors?timeRange=past365days&start=2024-08-11&end=2025-08-11&widget=organizations-leaderboard
- An anomaly in the dashboard data was noted that @tabathad will contact the LF about.
- @robmoffat is meeting with BMO soon and will raise the project with them.
- @andypols recent contributions were highlighted as valuable.
- There was consensus that the new maintainer appointments have/will help, but that recruiting more participants would strengthen the project further.
- New maintainers to contribute to trying to reduce the list of open issues and pull requests
- Remaining work on feat(key on repo url): support git hosts other than GitHub + multiple forks #1043
- Roadmap Roadmap - GitProxy v2 and beyond! #1119
- @jescalada has done some initial review of open issues to start us off on a roadmap
- There was consensus that a call/working session on the roadmap would help move things forward. @kriswest to host/send invite and invite @coopernetes (anyone else wishing to attend, please get in touch with @kriswest/comment on this issue). Time proposed Wednesday 13th Aug 1-2pm BST
- The question of what AI support is available in GitHub from FINOS - @mcleo-d to raise with FINOS board.
- Next meeting
- Falls on a UK bank holiday - there was consensus on pushing the meeting series back a week to avoid that
- @mcleo-d offered to plan the next meeting agenda - with a focus on marketing the project to help recruit adoptors and contributors.
Action Items
- @tabathad work with LF to correct project insights data.
- New maintainers (@kriswest @06kellyjac) to review GitHub actions (if they haven't already) and raise any questions about them
- New maintainers (@kriswest @06kellyjac) to review open issues and PRs and try to contribute to closing them/be ready to discuss in aa roadmap conversation
- @kriswest in feat(key on repo url): support git hosts other than GitHub + multiple forks #1043
- Check that we are validating the git URL are parseable URLs.
- After merge,
- Release notes to be drafted by kriswest on 2.0.0-rc.2 and to run the release (so he’s done it at least once)
- try to get @andypols PRs updated and merged in time for 2.0.0 release - but note Andy is OOO for a couple of weeks
- @kriswest to contact [email protected]:
- Mark 2.0.0-rc1 on NPM as a prerelease
- Push meeting series back a week to avoid UK bank holiday 25th Aug
- @kriswest Raise issue to update the GitHub action to tag prereleases based on version number content