09 March 2026 - GitProxy Meeting Minutes

[kriswest]

Date

20260309 - 16:00 GMT / 11:00 EST

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
  • 23rd Feb 2026 - GitProxy Meeting Minutes #1397
• Release 2.0 status
• Release branches
• New issues triage
  • Improve and standardize Agentic AI tooling #1410
  • Limit repos a user has access to #1415
  • Website deployment not reflecting changes from main #1418
  • Sort entries in the admin UI and apply proper pagination #1420
  • Improve API types and documentation #1430
• Revisit checkUserPushPermission is checking the wrong user's permission to push #1400 and feat(ssh): Add SSH agent forwarding #1332 - what can we do to validate the user doing the push?
• AOB, Q&A & Adjourn (5mins)

Meeting minutes

• Approved past meeting minutes
  The minutes from 23rd Feb 2026 (23rd Feb 2026 - GitProxy Meeting Minutes #1397) were approved with no objections.

• Release 2.0 status

  • The project is now very close to the 2.0 (RC5) release.
  • Final outstanding PRs are being coordinated for review and merge, particularly the logging improvements and TypeScript refactor.
  • The team resolved to focus on regression testing at multiple organisations after the RC5 candidate is merged.
  • Any issues found during full regression testing to be triaged for possible hotfixes prior to 2.0.
  • Known issues (e.g., checkUserPushPermission) remain explicitly excluded from the 2.0 release.

• Release branches

  • Discussion on future release strategy:
    • General agreement to keep trunk-based/main development as standard, only using release branches when absolutely necessary (e.g., for significant breaking changes).
    • Paul's (@grovesy) proposal: incrementally implement future major changes with adapters/shims to minimise breaking changes and avoid complicated branching.
    • @finos/git-proxy-maintainers to propose a low-res/high-level roadmap for upcoming releases, including the next minor version (2.1) and beyond, to help with release planning and feature/bug tracking.
    • Consideration of automating release notes and versioning with tools like Changesets.
    • All agreed to use visible tracking (e.g., GitHub project/milestone) for scoping minor releases and to set target release dates/deadlines.

• New issues triage

  • Improve and standardise Agentic AI tooling (Improve and standardize Agentic AI tooling #1410):
    • Initial PR submitted by @jescalada, currently based on existing organisational usage, but should be made agent-agnostic (e.g., rename from claude.md to agents.md).
    • Issue tagged as "good first issue" and "help wanted" for broader testing and feedback from different contributors and tools.
    • @Andreybest offered to help test and contribute.
  • Limit repos a user has access to (Limit repos a user has access to #1415):
    • Suggested by @andypols (not present for discussion), with focus on improving and/or making repository visibility configurable per user.
    • Discussed as a philosophical and practical change; to remain open for further comment and feedback.
    • @grovesy to reply and elaborate.
  • Website deployment not reflecting changes from main (Website deployment not reflecting changes from main #1418):
    • Issue considered resolved; website is currently deploying as expected.
    • Agreed to monitor future deployment failures via Netlify logs, and escalate to help@finos.org if necessary.
  • Sort entries in the admin UI and apply proper pagination (Sort entries in the admin UI and apply proper pagination #1420):
    • Basic sorting now merged (thanks to @andypols), but full pagination and search improvements required.
    • Issue remains open for additional work, with interest from external contributors and students.
  • Improve API types and documentation (Improve API types and documentation #1430):
    • Discussion on use of OpenAPI/Swagger to generate and maintain API documentation.
    • Recognised as valuable for external tool builders and internal maintainability.
    • Issue is "good first" for contribution, with AI tools suggested to bootstrap an initial spec.

• Revisit checkUserPushPermission and SSH Agent Forwarding

  • Not discussed in detail due to time constraints; rolled over to next meeting.
  • Remains a post-2.0 priority (see open action items).

• AOB, Q&A & Adjourn

  • Some suggestions for cleaning up old/superseded PRs related to licence headers and documentation.
  • Encouragement for all contributors to request addition to the Git Proxy Contributors Team for proper GitHub assignment and recognition.
  • A reminder to maintain and update "good first issue" tags to encourage new contributors.

Action Items

• @jescalada: Email help@finos.org regarding container registry and Docker image publication best practices, and update the team.
• @andypols: Continue UI JS/TS (MUI upgrade/Tailwind transition) investigations; keep team updated. Consider dual-UI approach.
• All maintainers: Review/merge remaining PRs/issues to complete v2 release checklist; support G-Research testing.
• @kriswest: Keep "checkUserPushPermission" refactor on agenda for post-2.0; initiate technical solution discussion.
• All: Review and provide feedback on notification system proposal (Extensibility through Event Hooks #1449) before next meeting.
• All: Continue to add/update "good first issue" tags where suitable.
• @jescalada: Raise issue/proposal to drop Node 20 support and update CI/test matrix, coordinating with @coopernetes.
• @grovesy: Draft a high-level/low-res roadmap for New workflow architecture #1383 as a basis for future release and refactor planning.
• @jescalada & @grovesy: Document evolving release branching and planning process in README or CONTRIBUTING.
• @kriswest/@grovesy: Confirm all regular contributors are invited to the Git Proxy Contributors Team; assist with access issues where required.
• @jescalada/@tabathad: Close or supersede old PRs/issues as discussed (e.g., legacy licence header PRs, docs PRs).
• @Andreybest: Continue assisting with reviews and onboarding-friendly issues.

Agenda items not discussed:

• Revisit checkUserPushPermission is checking the wrong user's permission to push (checkUserPushPermission is checking the wrong user's permission to push #1400) and feat(ssh): Add SSH agent forwarding (feat(ssh): Add SSH agent forwarding #1332) – ROLLED OVER

[06kellyjac]

@kriswest I think the calendar invite follows US Daylight savings so might be 15:00 GMT for a few weeks before we sync again on BST

[kriswest]

Minutes posted!

[re-vlad]

@kriswest , sorry for missing this. Ready to help with PR review, my github is : https://github.com/re-vlad (vladev)

[re-vlad]

@kriswest - following up action item: "Review/merge remaining PRs/issues to complete v2 release checklist". I wonder if the 2.0.0 is the current working list for the v2 release? It shows 9 open issues but no open PRs assigned to the milestone.

[jescalada]

@re-vlad The issue with the release items is this one: #1368

Since all of them have been merged, I made the v2.0.0-rc.5 release which is ready for testing!

[kriswest]

@re-vlad it looks like we abandoned the milestone and reworked the release scope via the issue @jescalada posted (#1368).

I have removed/descoped items that we did not undertake and commented on each.

@jescalada I've left two issues in scope that I think may actually be dealt with by your and @tabathad's contributions. If I am correct could you link them to the relevant PRs and then close the issues?

[kriswest]

@jescalada Tagging issues with milestones for release planning is what we should be doing as part of release planning. I'm behind on reading up on your proposals in that regard, but we should probably use the GitHub milestones feature to handle (and track progress against) the planned scope.

[jescalada]

@kriswest Thanks for pointing those out! I totally agree, we should do proper tracking with milestones and a release planning template (#1452) starting from 2.1.

I've gone and validated the remaining issues, there's a related PR for the documentation issue that should be ready to merge: #1385