Skip to content

9th February 2026 - GitProxy Meeting Minutes #1367

@kriswest

Description

@kriswest

Date

20260209 - 4pm GMT / 11am EST

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 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

(please add agenda items until 9th Feb)

Meeting minutes

GitHub username(s) not provided for:

  • Abdul Rahman (NatWest)
  • Vladimir Zateychuk

Meeting Minutes

  • New Participants:

    • Abdul Rahman (NatWest) and Vladimir Zateychuk introduced themselves as new joiners. Both encouraged to register for future meetings and provide GitHub usernames for tagging and participation tracking.
  • Approval of Past Meeting Minutes:

  • Proposal to Appoint Andy Pols as Maintainer:

    • Consensus reached to appoint @andypols as a Git Proxy maintainer, with majority maintainer approval. @kriswest to coordinate with FINOS to complete the process.
  • v2 Release – Status and Readiness:

    • Outstanding issues remain, including a bug fix (PR fix: improve handling of repository clones in the .remote folder #1393) and test coverage.
    • Agreement to produce a new release candidate (RC) once blockers are resolved, followed by comprehensive manual testing.
    • Documentation versioning deemed non-blocking for v2.
    • Recent successful testing by @tabathad noted.
    • Plan to back up G-Research contributions with reviews to accelerate progress.
  • Setting up CODEOWNERS:

    • Discussion on CODEOWNERS configuration; @jescalada to add @andypols once appointed.
    • Agreement to avoid single-person dependencies by ensuring fallback to the maintainers group.
    • All maintainers to review and update the branch for CODEOWNERS setup before next meeting.
    • @kriswest to liaise with FINOS regarding repository settings and review rights.
  • e2e Test Issues:

    • Clarified that certain test data references are faked, not live.
    • @coopernetes to raise an issue and clean up naming for clarity.
    • Documentation improvements planned:
      • Better instructions in CONTRIBUTING.md for running E2E and other tests locally.
      • Rationalise developer documentation between repo and website; technical content to live in-repo, governance/process on the website.
      • @coopernetes volunteered to lead the documentation rationalisation.
  • v2.1 Scope:

    • Brief discussion; SSH agent forwarding (G-Research), hybrid cache (@fabiovincenzi), annotated tag push
    • Improved logging highlighted for 2.0 release @RichardUri
    • @AndyPol to continue work on their 2.1 items.
  • AOB, Q&A:

    • Use case shared by @andypols regarding Git Proxy for closed-source, cross-company collaboration (not just open source).
    • Discussion on Renovate PR/issue noise; suggestion to further automate merges if test coverage is sufficient.
    • @Andreybest volunteered to review and improve Renovate configuration.

Action Items

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions