17th November 2025 - GitProxy Meeting Minutes #1269
Description
Date
20251117 - 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 and review eeview Meeting Notices (see above)
- Approve past meeting minutes
- Discuss status of TS conversion PRs
- Questions from potential new adopters
- AOB, Q&A & Adjourn (5mins)
Meeting Minutes
-
New Participant Introduction
- @RichardUri (Citi) introduced himself as a full-stack developer working under @grovesy and is excited to contribute to the project.
-
Approval of Previous Meeting Minutes
- No objections to the previous meeting minutes (3rd November 2025 - GitProxy Meeting Minutes #1259) were raised. Action items from the prior meeting were addressed or rolled over as needed.
-
Status of TypeScript Conversion PRs
- @jescalada’s Vite/Vitest testing PR has had significant review by @kriswest, with issues outside the PR's scope to be raised separately. @jescalada agreed to address review comments and problematic tests have been isolated. Dockerised test setup (led by @coopernetes) is being considered to help with side-effect issues and CI sandboxing.
- Types consolidation PR was merged after review by @andypols. Discussion included the config schema documentation generation process, with suggestions to clarify Python dependency requirements in documentation.
-
Status of SSH implementation effort
- SSH-related PRs and agent forwarding implementation are progressing (significant contributions by @fabiovincenzi on top of @dcoric's work), with input from Citi contributors welcomed for architectural review.
-
Repository Caching and Performance PRs
- @fabiovincenzi reported the repository caching PR is updated and ready for additional review, having incorporated feedback from @06kellyjac and @jescalada.
-
UI Route Authentication Refactor
- @jescalada acknowledged an outstanding UI root authentication issue, will raise it formally though it is not currently high priority.
-
Release Candidate and Minor Updates
- Plan to roll RC4 after merging the Vite/Vitest and license header PRs. Minor PRs such as Renovate updates will be included as appropriate. Pagination and minor UI improvements were discussed to enhance the user experience.
-
Notification System Design
- @06kellyjac will draft a high-level outline for notification system design, inviting comments from other maintainers and adopters.
-
Alternative Email Support
- @06kellyjac retains the action to revise the PR for alternative email support, handling the distinction between commit and login emails.
-
MongoDB Integration Tests
- @dcoric will coordinate with @coopernetes to review progress and next steps for dockerised testing and MongoDB integration, superseding the previous open action item.
-
Questions from Potential New Adopters
- Recent outreach from JP Morgan and Deutsche Bank was noted, prompting a discussion on improving project documentation and website content to support onboarding. @tabathad will review and suggest documentation clustering and minimal refreshes.
-
AOB, Q&A
- @kriswest encouraged the use of GitHub Discussions, Issues, and Finos Slack for sharing opportunities and support queries. The next RC is planned, after which the v2.0 scope will be reviewed. An open call for agenda items and input for the next meeting was made.
- No additional business or urgent questions were raised.
Action Items
- @jescalada to address review comments for the Vite/Vitest PR, raise issues for out-of-scope comments, and coordinate resolution.
- @jescalada to create and address an issue for UI route authentication.
- @dcoric to catch up with @coopernetes about dockerised testing and MongoDB integration.
- @fabiovincenzi to continue agent forwarding (SSH) implementation and update the group at the next meeting.
- @kriswest to raise an issue to improve "getting involved" content and general project documentation.
- @tabathad to review existing documentation and recommend minimal refreshes, grouping topics as needed.
- @06kellyjac to draft a notification system design outline and continue work on the alternative email support PR.
- All maintainers to review the repository caching PR (feat: implement hybrid cache architecture #1246) and Vite/Vitest testing PR when ready.
- @kriswest to review open issues prior to the next release candidate.
- All to raise minor UI improvements (e.g., pagination) as required.
- All to contribute to improving documentation and onboarding content as time permits.
- All to use GitHub Discussions/Issues/Slack to share opportunities for project advocacy and recruitment.