Date
20260713 - 4pm BST / 11am EDT
Meeting info
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
Meeting Minutes
Meeting Minutes
-
New Participants Introduced
- Morgan Thomas (work experience via Rob Moffat) introduced himself.
- Kaitlynn and the group of NatWest interns introduced themselves as part of the summer OSPO team.
-
Approval of Previous Meeting Minutes
-
Previous Action Items
- Several items were marked as complete, including automation of version bumping workflow, reassignment and relabelling of issues, and PR reviews.
- The architecture/workflow roadmap workshop is still pending. @Andreybest volunteered to contact @grovesy to clarify next steps.
- Internal security requirements for storing credentials need further input; @kriswest and @andypols to coordinate.
- Incorporation of Agentic workflow feedback is deferred to a future meeting.
- All are encouraged to actively propose topics for next meetings and resolve any merge conflicts as assigned.
-
2.1 Milestone PRs
feat: add tsoa for API type control and documentation #1501:
- Discussion centred on the now-unmaintained TSOA library. Several alternatives (TS REST, NestJS, Adonis.js) were discussed, with a preference for a well-maintained solution.
- Decision: De-scope this PR from 2.1; @Andreybest will attempt a new approach based on group discussion.
ci: refactor workflows for release branching #1520:
- Marked as complete. @jescalada to produce a demo video of the release workflow for documentation.
feat(upstream-proxy): add HTTP Basic and NTLM auth methods #1551:
- Identified edge cases with chunked 407 responses. Most environments unaffected, but a health warning and code comment are to be added. May move to 2.2 if not completed for 2.1.
-
Contribution Speed Issues
- Broad agreement that review/merge speed is a bottleneck, primarily due to limited reviewers and a policy requiring reviews from other firms.
- Discussed relaxing the policy to allow reviews from maintainers within the same firm, provided it is not self-approval.
- Plan to appoint more maintainers, especially from @jescalada/@kriswest (@G-Research, @Citi) teams.
- Consensus to pursue more frequent, smaller releases rather than holding work for milestones.
-
Fogwall Feature Porting PRs
- Live feedback during pushes, error collection, and disconnect detection features were reviewed:
feat: add live feedback during pushes (sideband streaming) #1637: Approved pending auto-merge after checks.feat: execute all steps and collect errors at end of chain #1640: Feedback to remove config setting and possibly allow plugins to self-declare error behaviour. To be updated and re-approved.feat: implement disconnect detection, cancel pushes on disconnect #1641: Explanation provided; still in draft. Testing challenges noted. Will remain draft while further experimentation occurs.
- Plug-in architecture needs to be extended to support UI notifications/advisories, not just action lists.
-
GitProxy Health Report + TOC Presentation
- @jescalada preparing for TOC presentation (technical-oversight-committee#299). @kriswest to review the document. Encouraged to highlight active contribution and project relevance.
- @jescalada will present; other maintainers welcome but not required.
-
Deprecation Warnings for Legacy Config Fields
feat(config): add deprecation warnings for legacy config fields (Phase 1: warnings in 2.x) #1626:
- Proposal to warn users in 2.x, with breaking changes in 3.x.
- Feedback given to pull deprecation info from config schema, using descriptions for replacement suggestions.
-
OSFF New York (November) GitProxy Booth
- @jescalada plans to staff the booth and is considering submitting a talk.
- Encouragement provided to submit a session talk, with reassurance about the supportive conference environment.
- Discussion on content and flyer updates; @jescalada to coordinate with FINOS events lead (Eteri).
-
AOB / Q&A
- Discussion on blog/article tone for upcoming GitProxy communications—should balance technical/corporate messaging for both OSPO and developer audiences.
- Noted need to review and merge the event notification/handler PRs, particularly for email notification support.
-
Not Discussed
- No items skipped; all agenda topics were addressed, though some (like Agentic workflows) were deferred for future meetings.
- No substantial open Q&A/AOB topics, beyond blog/article and booth planning.
Action Items
Date
20260713 - 4pm BST / 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
Meeting Minutes
Meeting Minutes
New Participants Introduced
Approval of Previous Meeting Minutes
Previous Action Items
2.1 Milestone PRs
feat: add tsoa for API type control and documentation #1501:ci: refactor workflows for release branching #1520:feat(upstream-proxy): add HTTP Basic and NTLM auth methods #1551:Contribution Speed Issues
Fogwall Feature Porting PRs
feat: add live feedback during pushes (sideband streaming) #1637: Approved pending auto-merge after checks.feat: execute all steps and collect errors at end of chain #1640: Feedback to remove config setting and possibly allow plugins to self-declare error behaviour. To be updated and re-approved.feat: implement disconnect detection, cancel pushes on disconnect #1641: Explanation provided; still in draft. Testing challenges noted. Will remain draft while further experimentation occurs.GitProxy Health Report + TOC Presentation
Deprecation Warnings for Legacy Config Fields
feat(config): add deprecation warnings for legacy config fields (Phase 1: warnings in 2.x) #1626:OSFF New York (November) GitProxy Booth
AOB / Q&A
Not Discussed
Action Items