Skip to content

15th December 2025 - GitProxy Meeting Minutes #1300

New issue
New issue
Open
Open
15th December 2025 - GitProxy Meeting Minutes#1300
Labels
meeting
@kriswest

Description

@kriswest
kriswest
opened on Dec 1, 2025

Date

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

Meeting Minutes

  • Past meeting minutes from 1st December (1st December 2025 - GitProxy Meeting Minutes #1289) were reviewed; no major corrections raised. Outstanding action items remain.
  • PI test TS and Dockerised testing PR merge conflicts are in progress (@coopernetes addressing merge conflicts).
  • Homepage testimonial review and social media strategy: discussed the need for more testimonials, especially LinkedIn stories, to be contributed by various organisations. All encouraged to submit new content to display on the homepage.
  • Hybrid cache architecture was discussed; outstanding review and concerns about single branch checkout and concurrency remain. No further progress.
  • Notification system design: remains unaddressed; @06kellyjac is expected to look into this in the new year, with @andypols and @kriswest also interested.
  • SSH forwarding PR: @fabiovincenzi confirmed GitLab compatibility and is finalising the PR. Setup instructions will need updates to cover provider variants.
  • Race condition in FileDB config: fix is merged, but more issues may exist due to import order; team to remain vigilant for related bugs.
  • CLI coverage issue: @jescalada to raise an issue to track work.
  • Failing proxy tests: ongoing, further diagnostics needed to identify which test leaves a proxy open.
  • JWK-to-PEM dependency removal (PR fix: drop dependency on jwk-to-pem by using native crypto #1283): needs final external review (@coopernetes to review).
  • Website homepage improvements: PR by @tabathad is ready; minor adjustments needed, including testimonial ordering and content updates.
  • V2 release process: migration guide (Git proxy 2.0 migration guide #1324) raised. Documentation (including getting started/config guides and doc versioning) is a key blocker for release. Docusaurus versioning to be implemented (@kriswest to raise an issue).
  • Migration guide and docs versioning: will snapshot 1.x docs for historical reference; @tabathad to address quick fixes and raise issues for new V2 documentation needs.
  • Deprecated properties in FileDB config are removed; further work to improve pagination defaults and config schema is pending.
  • Major open PRs and issues reviewed:
  • V2 release priorities: team agreed to prioritise essential/breaking changes for 2.0 and defer some features/PRs to 2.1/2.2 releases. SSH support will be included in a subsequent minor release if not fully reviewed/polished in time.
  • Backporting fixes to 1.x: @coopernetes will selectively backport critical fixes for a final 1.x release.
  • Dynamic frontend base URL handling (Handle frontend base URL dynamically for production deployments #1302) is implemented and included in the end-to-end testing PR by @coopernetes.
  • Docker/OCI image for GitProxy (Create & publish OCI image for GitProxy with production use #1303): Dockerfile integration is ready; publishing to follow after V2 release.
  • Support for proxying non-TLS HTTP repos (Support proxying HTTP (non-TLS) git repos #1304): reserved for testing/development, not prioritised for production, may be dropped if self-signed TLS is sufficient.
  • Required vs. optional top-level config schema (Require top-level config values while allowing to override config file #1287): further work needed but not critical for V2.
  • Automate in-house fork sync with upstream (Automate the sync of in-house forks with upstream repositories #1240): not explicitly discussed.
  • GPG/SSH commit signature verification (GPG/SSH commit signature verification #1321): not explicitly discussed.
  • General agreement to cancel the next meeting scheduled for 29th December; next meeting in early January.

Action Items

  • @coopernetes to resolve PI test TS and Dockerised testing PR merge conflicts.
  • All: Provide new LinkedIn testimonials/stories for homepage; notify @tabathad for inclusion.
  • @06kellyjac to address notification system design or group to schedule session if unavailable.
  • @fabiovincenzi to finalise and push SSH forwarding PR for review.
  • @jescalada to raise issue for CLI coverage.
  • @jescalada (with team) to continue diagnosing and fixing failing proxy tests.
  • @coopernetes to review JWK-to-PEM removal PR (fix: drop dependency on jwk-to-pem by using native crypto #1283).
  • @tabathad to submit a PR for homepage quick fixes and raise issues for new V2 documentation needs.
  • @kriswest to raise an issue for Docusaurus docs versioning and snapshot 1.x docs.
  • @andypols to split error message UI improvements and reject reason features into smaller PRs.
  • @fabiovincenzi to request review of SSH UI PR once ready.
  • @kriswest and @jescalada to review and update the V2 milestone/issues list to match current status.
  • @coopernetes to selectively backport critical fixes to 1.x and raise PRs as needed.
  • @tabathad, @kriswest, @coopernetes et al. to contribute to a new architecture/‘Developing Against GitProxy’ doc/README.
  • @sam-holmes2 to resolve outstanding conflicts and finalise Apache-2.0 license headers PR (fix: Add Apache-2.0 license headers to source files (2) #1253).
  • Team to review and test dynamic frontend base URL handling in Docker Compose/end-to-end testing PR.
  • @andypols to investigate/refactor UI JS/TS code and support transition from Material UI to Tailwind (as desired).
  • All to raise any breaking changes needed for V2 as soon as identified.
  • @jescalada to suggest/test testimonials ordering on homepage PR.
  • @kriswest to coordinate merging homepage PRs when ready.

Not discussed:

Metadata

Metadata

Assignees

No one assigned

    Labels

    meeting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions