23 March 2026 - GitProxy Meeting Minutes

[kriswest]

Date

20260323 - 3pm GMT / 11am 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
  • 09 March 2026 - GitProxy Meeting Minutes #1416
• v2 release status + testing rc-5
• Project infrastructure: Add E2E Tests as required status check on CI #1460
• Issues with PRs
  • Improve pagination defaults and layout in admin UI #1297 / Sort entries in the admin UI and apply proper pagination #1420
    • feat: add server-side pagination to API endpoints #1464
  • Enable TLS for UI and API #1408
    • feat: add TLS support to API/UI service #1414
• Recent issues to be discussed:
  • GitProxy as a GitHub/GitLab App #1450
  • Limit repos a user has access to #1415
  • Pushes in the 'error' category don't render in the admin UI unless a diff was produced #1387
  • Unify repository and website documentation #1407
  • Improve API types and documentation #1430
  • Extensibility through Event Hooks #1449
  • Architecture - Phase 1 - Creating room #1451
• Release branches - what next?
• Introducing AI policy?
• AOB, Q&A & Adjourn (5mins)

Meeting Minutes

• Approve past meeting minutes

  • Previous minutes (09 March 2026 - GitProxy Meeting Minutes #1416) reviewed; carried forward action items discussed and updated.

• v2 release status + testing rc-5

  • Release Candidate 5 (RC5) for v2.0 created; limited manual testing completed with no new issues found, but request for broader UI testing from teams who use the UI directly.
  • Plan to complete further testing before the next meeting.
  • Node 20 deprecation and related docs merged since RC5; discussion whether to cut RC6, but agreement to tag 2.0.0 directly unless showstopper issues arise.
  • Final release will include docs and Node 20 deprecation; remaining dependency bumps (PRs) to be merged before tagging 2.0.0.

• Project infrastructure: Add E2E Tests as required status check on CI (Add E2E Tests as required status check on CI #1460)

  • End-to-end (E2E) workflow should be required on CI; @kriswest will contact help@finos.org to have this enforced.

• Issues with PRs

  • Pagination and Admin UI (Improve pagination defaults and layout in admin UI #1297, Sort entries in the admin UI and apply proper pagination #1420, feat: add server-side pagination to API endpoints #1464):
    • Ongoing work on server-side pagination and sorting in the admin UI; @fabiovincenzi leading.
    • Appreciation for recent improvements making the UI more usable; post-v2 release priority.
  • Enable TLS for UI and API (Enable TLS for UI and API #1408, feat: add TLS support to API/UI service #1414):
    • TLS support for API/UI merged or pending review; ensure documentation covers relevant config.
  • No further discussion on these PRs; others to review and merge as needed.

• Recent issues to be discussed:

  • GitProxy as a GitHub/GitLab App (GitProxy as a GitHub/GitLab App #1450):
    • Discussed value of developing first-class GitHub/GitLab integrations, particularly for internal SCM and improved authentication/auditability.
    • Noted that OAuth-style integrations and more granular API access could address several user journey and security requirements; agreed to revisit and research for next meeting.
  • Other recent issues (Limit repos a user has access to #1415, Pushes in the 'error' category don't render in the admin UI unless a diff was produced #1387, Unify repository and website documentation #1407, Improve API types and documentation #1430, Extensibility through Event Hooks #1449, Architecture - Phase 1 - Creating room #1451):
    • No detailed discussion in this meeting; deferred to next meeting with a plan to prioritise issues for upcoming releases.

• Release branches – what next?

  • Discussion on future branching strategies post-v2.0, including possible adoption of a GitLab Flow-like strategy for easier merging and conflict management.
  • @jescalada to document the agreed branching model and provide recommendations; compare/contrast with GitHub milestones and issue-based planning.

• Introducing AI policy?

  • Support for an agents.md or similar file to formalise acceptable AI usage and agent behaviour; @re-vlad to progress improvements/build on @jescalada's initial PR.
  • Reference to context from architecture guide to be included.

Action Items

• @jescalada: Email help@finos.org regarding container registry and Docker image publication best practices; update the team.
• @andypols: Continue UI JS/TS (MUI upgrade/Tailwind transition) investigations; keep team updated. Consider dual-UI approach.
• @kriswest: Keep "checkUserPushPermission" refactor on agenda for post-2.0; initiate technical solution discussion.
• All: Continue to add/update "good first issue" tags where suitable.
• @grovesy: Draft a high-level/low-res roadmap for New workflow architecture #1383 (workflow/new architecture); clarify scope and update next meeting.
• @kriswest: Email help@finos.org to require E2E workflow for CI (Add E2E Tests as required status check on CI #1460).
• @kriswest: Provide feedback on the notification system proposal, focusing on integration approaches (config vs code, built-in handlers, webhooks).
• @jescalada: Document the proposed release branching and planning process (issue planning vs milestones) and seek consensus.
• @jescalada: Review whether docs and node 20 deprecation are included in 2.0.0 tag; coordinate tagging/release as needed.
• @coopernetes: Merge remaining dependency bump PRs to fully deprecate Node 20 support.
• @re-vlad: Improve and extend agents.md/AI policy file, ensuring context from architecture guide is included. Improve and standardize Agentic AI tooling #1410
• All: Review open issues/milestones; bring team's priorities/long-term goals to the next meeting for release planning.
• All: Teams to commit to v2.0 RC5 testing and sign-off, especially for UI coverage, before next meeting.