Skip to content

12 January 2026 - GitProxy Meeting Minutes #1327

@kriswest

Description

@kriswest

Date

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

Meeting Minutes

  • New participant introduction: Maahir Chauhan joined for the first time, introduced themselves as a full-stack developer from India with experience in CNCF projects. Assistance was offered for joining the community Slack.

  • Approve past meeting minutes and previous actions review:

    • Completed action items were confirmed and checked off.
    • Uncompleted items were agreed to roll over, or clarified for next steps.
    • Some actions (e.g. homepage PR coordination) were closed or merged with others.
  • v2 Release Documentation PRs:

    • @jescalada has drafted and opened two major docs PRs:
    • Feedback was given on the need to clarify target audiences in documentation (admins vs users vs developers). @andypols will raise an issue to reorganise docs around these roles.
  • SSH Implementation PR:

    • @fabiovincenzi reported PR feat(ssh): Add SSH agent forwarding #1332 for SSH agent forwarding is open, with additional tests added.
    • Coverage numbers discussed; some discrepancies between CI and codecov reporting noted.
    • Review requested from all, especially those deploying SSH features.
    • @jescalada to raise an issue to investigate coverage reporting accuracy.
  • Publish on Release Error (NPM pre-release fail, Failure to publish to NPM on pre-release #1334):

    • Pre-release to NPM failed due to expired/revoked classic tokens; session-based tokens now needed, with 90-day expiry and 2FA.
    • @jescalada to escalate to FINOS admin/[email protected] and TOC for guidance and solution, noting other projects may be impacted.
  • Gauge Interest on Docker Hub Auto-publish:

    • Discussed pros and cons; agreed auto-publishing would help adoption and mirror established FINOS project practices.
    • @jescalada to enquire with FINOS about recommended registry (Docker Hub vs GitHub Container Registry) and process.
  • Remove dependence on jsdelivr.net and chartist.js Remove dependence on jsdelivr.net and possible unneeded dependency on chartist.js #1344:

    • @kriswest will PR to eliminate jsdelivr CDN usage for dependencies (security/governance), and remove unused chartist.js if possible. No objections raised.
  • Error messages in Admin UI when not logged in, broken login link Error messages displayed in admin UI when not logged in and broken login link #1345:

    • @jescalada has a quick fix for the issue and will open a PR; further review by @kriswest flagged for correct conditional handling.
  • AOB:

    • @andypols shared successful deployment of GitProxy behind their load balancer after resolving authentication/load balancer edge cases.
    • No further urgent topics raised due to time constraints.

Agenda Items NOT Discussed

  • Milestone/issues list review and update (planned for next meeting due to lack of time)
  • GPG/SSH commit signature verification (deferred)
  • Proposed discussion on GitProxy’s role in ingress/monitoring, and dependency scanning features (deferred)

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