1st June 2026 - GitProxy Meeting Minutes

[kriswest]

Date

20260601 - 4pm BST / 11 EDT

Meeting info

• Meeting link

• Register for future meetings

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 legal@finos.org 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 and review Meeting Notices (see above)
• Approve past meeting minutes
  • 18th May 2026 - GitProxy Meeting Minutes #1524
• Finalise and merge MAINTAINERS.md: docs: add MAINTAINERS.md file #1547
• fix: apply security best practices #1548
• Review catch-up
  • 35 Open PRs: https://github.com/finos/git-proxy/pulls
  • Start with 2.1.0 priorities: https://github.com/finos/git-proxy/milestone/10
  • 10 renovate PRs: https://github.com/finos/git-proxy/issues?q=is%3Apr+is%3Aopen+author%3Aapp%2Frenovate
  • Request to prioritise: feat: expose service module through package exports (#1539) #1542
• AOB, Q&A & Adjourn (5mins)

GitHub username not provided for:

• Tomasz Swierszcz (Citi)

---

Meeting Minutes

Past Meeting Minutes Approval

• Minutes from the 18th May 2026 (18th May 2026 - GitProxy Meeting Minutes #1524) were approved.

MAINTAINERS.md Finalisation

• All maintainers except the emeritus maintainer have updated their details in MAINTAINERS.md.
• Jamie (@JamieSlome) has been tagged to confirm if he wishes to remain; group agreed to wait a few days before removing him if no response.
• Citi contributors encouraged to nominate another maintainer via PR, as @grovesy is unavailable and Citi contributions have increased.

OSFF London Presentation & Booth Support

• Booth allocation still pending with FINOS. @kriswest is awaiting an update.
• Vlad (@re-vlad) to contact Tomasz and Citi team to confirm attendee list and coordinate on booth support.
• Tomasz to circulate a summary or draft of the OSFF Git Proxy presentation for group feedback before the next meeting; Vlad to follow up and suggest use of a GitHub issue for summarising/discussion.

Workflow/Architecture Roadmap

• No progress reported on updating the architecture roadmap or linking workflow issues (New workflow architecture #1383, Architecture - Phase 1 - Creating room #1451). Item rolled over.

Automating Version Bumping

• No progress yet from @jescalada on automating version bumping and ensuring package.json version/tag workflow matches (Improve/automate package.json version bumping on NPM publish & release drafter #1533, Tweak workflow files to work with GitLabFlow branching #1517). Item rolled over with suggestion to use a well-known library.

MongoDB Migration Requirements

• @re-vlad reported the MongoDB migration MR is ready; all comments addressed and waiting for further review. Testing on FileDB is outstanding—@re-vlad to test and update or clearly document limitations.

Date Created Repo Sorting

• No further work has been done; issue to be included and tracked with upcoming UI work. Will be handled as part of a future milestone (2.2). Previous action to liaise on implementation is now considered complete.

Windows CI Test Failures on SSH Agent Forwarding

• Issue resolved and fix merged. No recent failures observed.

API Documentation PR Chain Merging

• @fabiovincenzi to retarget his PR onto @Andreybest’s branch. Both to ensure generated code is committed and routes are correctly rebuilt on proxy restart. Ongoing.

SSH PRs Review/Testing

• SSH Agent Forwarding (feat(ssh): Add SSH agent forwarding #1332) and Annotated Tag Push Support (feat: Add Annotated Tag Push Support #1139) PRs require urgent cross-org review and approval. Action reaffirmed for all maintainers.
• Discussion highlighted need for more reviewers to avoid PR backlog; @andypols and Citi contributors to prioritise review before next meeting.
• Outstanding minor issue on SSH PR regarding merge commit handling; @jescalada to clarify if it is reproducible and improve error messaging, but not a blocker for merge.

Documentation Improvements

• All asked to propose further doc/template improvements as needed. Suggestion to optionally include screenshots/demos in PRs (not mandatory due to organisational restrictions).

feat(ssh): Add SSH Agent Forwarding #1332

• See SSH section above for discussion and current status.

fix: apply security best practices #1548

• @jescalada to unify Dependabot/Renovate configs, preferring a move to Dependabot based on group consensus. Will implement with weekly updates and delayed update feature.

Review Catch-Up

• Prioritised PRs for v2.1.0: SSH support, tag support, default admin user creation, and others. All linked PRs need review.
• Renovate PR backlog noted; group agreed to migrate to Dependabot to simplify and improve workflow.

Request to Prioritise: feat: expose service module through package exports (#1539) #1542

• Discussed in detail: Not opposed to exposing service info, but maintainers recommend using getter functions and moving legacy env var config into main config schema for consistency. @re-vlad and @rajeevr-g to adjust implementation accordingly.

AOB

• Topic of Java version of Git Proxy to be added to next agenda for discussion with @coopernetes (Thomas Cooper).
• Welcome to @rajeevr-g (Citi), attending as new participant.

---

Action Items

• Tomasz Swierszcz (Citi): Coordinate with Citi team for OSFF booth support, update @kriswest with attendee list (Vlad to follow up).
• Tomasz Swierszcz (Citi): Circulate summary/draft of OSFF Git Proxy presentation to group via GitHub issue for feedback.
• @grovesy: Update architecture/workflow roadmap, link relevant issues (New workflow architecture #1383, Architecture - Phase 1 - Creating room #1451).
• @jescalada: Continue work on automating version bumping, ensure workflow sets package.json version/tags during releases (Improve/automate package.json version bumping on NPM publish & release drafter #1533, Tweak workflow files to work with GitLabFlow branching #1517).
• @re-vlad: Test MongoDB migration (Proposal: Automated MongoDB Migration Script from v1.19.2 to v2.0.0 upgrade #1535) against FileDB; update docs or implementation based on results.
• @Andreybest / @fabiovincenzi: Coordinate chain merging of API docs PRs, ensure generated code is committed and routes rebuilt on restart.
• @ALL: Review and test SSH Agent Forwarding (feat(ssh): Add SSH agent forwarding #1332) and Annotated Tag Push Support (feat: Add Annotated Tag Push Support #1139) PRs before next meeting.
• @jescalada: Update error messaging for unreferenced commit handling in both SSH/HTTP flows, if possible.
• @fabiovincenzi: Retarget API doc PR onto @Andreybest’s branch for coordinated merge.
• Citi Team: Discuss and nominate an additional maintainer via PR to MAINTAINERS.md.
• @jescalada: Switch project from Renovate to Dependabot, configure for weekly updates and delayed update feature; migrate relevant settings, remove Renovate after confirmation.
• @rajeevr-g: Adjust PR to use getter functions for service config; avoid direct import of .env, and consider refactor to add legacy env vars to config schema.
• @kriswest: Add Java version of Git Proxy (Thomas Cooper) to next meeting agenda.
• @kriswest: Remind/track response from @JamieSlome regarding maintainership; proceed to remove if no response within a few days.