Skip to content

26th January 2026 - GitProxy Meeting Minutes #1364

@kriswest

Description

@kriswest

Date

20260126 - 4pm GMT / 11am EST

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

Minutes

  • New participant: Andrii Kotliar introduced himself as a new contributor, working with @grovesy.
  • Previous Action Items Review:
    • Significant action items from the previous meeting were reviewed, with progress on most items. Several are ongoing or rolling over (see action items below).
    • @tabathad confirmed homepage quick fixes are nearly complete—waiting on a title for Jamie; suggestion to proceed with "Emeritus maintainer."
    • Ongoing work on failing proxy tests, Windows test support, and test coverage improvements led by @fabiovincenzi and @jescalada.
    • Notification system design discussion: @grovesy volunteered to write up a proposal for a hooks-based notification architecture.
    • Docs reorganisation and user/developer/admin split to be advanced by @andypols.
    • V2 upgrade doc and architecture guide need more feedback from the broader team.
    • Open PRs for licence headers (Apache-2.0) to be split into config and mass-update steps; @06kellyjac to take over from @sam-holmes2.
    • UI improvements (error message/reject reason) being split into smaller PRs by @andypols.
    • DocuSaurus versioning and snapshotting by @kriswest pending completion of pending doc PRs.
    • Docker image publication pattern and container registry queries ongoing with FINOS by @jescalada.
  • Issues and PR List Bloating:
    • Noted large and growing backlog of issues and PRs, including legacy Citi Hackathon PRs and old Renovate bot PRs.
    • Maintainers encouraged to triage, label, and close stale issues/PRs where appropriate.
    • @RichardUri agreed to review Citi Hackathon PRs for possible revival or closure.
    • Discussion of labelling, "good first issue", "help wanted", "wontfix", and collaborative hygiene.
  • Governance and Codeowners:
    • Discussion on main repository review/merge rights after a PR was merged without review, which broke the build.
    • Proposal to set up CODEOWNERS to assign specific maintainers to paths and require reviews, adjusting rights where justified (e.g., for CI-related scripts).
    • @kriswest to contact [email protected] and @coopernetes about reviewing and tightening repo settings, and to explore implementing CODEOWNERS.
    • Consensus that PRs should always have a second pair of eyes unless CODEOWNERS allows otherwise.
  • V2 PRs and Work Remaining:
    • V2 punch list requested for outstanding PRs/issues required for the release; maintainers to prioritise.
    • SSH support PR deferred to 2.1 due to setup complexity and required review.
    • Test coverage improvements are ongoing (@fabiovincenzi, @jescalada, @dcoric).
    • Invalid regex validation PR is ready for review and inclusion.
    • Annotated tag push improvements requested by G-Research; targeted for 2.1.
    • Ongoing work on dynamic frontend base URL in Docker Compose—likely resolved but to revisit if issues arise.
    • Hybrid cache PR is out of scope for V2 but important for post-V2 performance.
    • End-to-end Mongo testing on CI is work-in-progress (@dcoric).
    • Renovate PRs and large dependency updates to be triaged around or after V2.
    • Accessibility review for UI to be conducted as a training task for a new joiner on @kriswest’s team.
    • Material UI (MUI) upgrade and/or transition to Tailwind under consideration by @andypols’s team; not planned for V2.
  • AOB, Q&A & Adjourn:
    • Discussed meeting running length—agreed to update meeting calendar to a full hour (@kriswest).
    • @andypols proposed as a maintainer; @kriswest to raise the nomination issue.
    • Reminded new contributors (e.g., Andrii) to raise issues and PRs for installation/packaging bugs.
    • General encouragement to continue reviewing, closing, and prioritising open issues and PRs.
    • Security and governance processes around repo access and internal org policy were discussed.

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