Skip to content

13th April 2026 - GitProxy Meeting Minutes #1471

Closed
Closed
13th April 2026 - GitProxy Meeting Minutes#1471
Labels
meeting

Description

@kriswest
kriswest
opened on Mar 23, 2026

Date

20260413 - 11am EDT / 4pm BST

Monday 6th April is Easter Monday so this meeting has been deferred a week to 13th April

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

Minutes

  • Previous meeting minutes were reviewed and approved.

    • Several prior action items were discussed, with updates or closure captured in the action list below.
    • The action item for @jescalada to email help@finos.org regarding container registry best practices was dropped from tracking by group consensus.
    • Noted that @grovesy’s roadmap action remains open and will be kept on the action list until updated.
    • @re-vlad’s action on improving agents.md/AI policy file remains in progress and will stay on the action list.
    • Testing and sign-off for v2.0 RC5 was discussed; RC6 testing is to follow pending final PR merge.

  • @andypols presented a revamped and updated UI demo for GitProxy.

    • Major changes: migrated from MUI->Tailwind, adopted GitHub’s UI controls, updated navigation, improved caching for API rate-limited calls, and enhanced sorting/filtering in the repositories dashboard.
    • Added support for alternate emails; improved admin/user management flows; fixed reviewer and permissions UI annoyances.
    • The UI is now responsive for mobile devices. Additional features include improved handling of forked repositories, and new caching for metadata.
    • Future: Plan to allow plugins to extend UI, improve error handling and permission logic, and add screenshot(s) to an appropriate issue (with data redacted where necessary).
    • Feedback was very positive from the group, with consensus to work towards landing the new UI in an upcoming minor release (target 2.2).

  • Pending PR (fix(plugins): update sample plugin imports to use package subpath exports fix(plugins): update sample plugin imports to use package subpath exports #1484) and V2 RC6 release process.

    • The PR is blocking RC6; @jescalada will merge after confirming with @coopernetes (whose org relies on plugins) or proceed with a patch if issues arise post-merge.
    • Once merged, RC6 will be cut. Teams to test RC6 and report any issues prior to promoting to v2.0.

  • Roundtable: Organisational goals for GitProxy

    • @kriswest (NatWest): Emphasised reducing friction for developer open source contribution, making onboarding/audit trails easier, embedding with internal AI/automated tooling, and eventually supporting ingress risk evaluation for supply chain security.
    • @tabathad (G-Research): Similar friction-reduction goals, adding value of surfacing contribution data, health metrics, and possibly tying open source activity to internal volunteer programmes.
    • @andypols (Qube): Focus on end-to-end open source lifecycle, streamlining PR syncing/approvals, and enabling more seamless interaction with GitHub (and potentially other Git forges in future).
    • @re-vlad/@Andreybest (Citi): Awaiting v2.0 release and working through priorities; architecture issues and roadmap to be discussed further at upcoming meetings.
    • General agreement: Long-term goals are to provide a fully auditable, low-friction platform for open source engagement, with extensibility for notifications, AI-integration, and supply chain controls.

  • Plan next GitProxy release milestone

    • RC6 release is imminent; the focus remains on testing and promotion to v2.0.
    • For v2.1/v2.2, the new UI is a top candidate, with other features to be tagged and milestones refined.
    • All participants to review open issues and tag those ready for 2.1 in the milestone for discussion at the next meeting.

  • AI Policy Discussion

    • Deferred to GitHub issue for asynchronous discussion; not discussed in detail during meeting.

  • Issues with authentication & GCM

    • Briefly raised by @kriswest: difficulties for first-time users with Git Credential Manager and Git Proxy authentication. Will be documented in an issue for further investigation/discussion.

  • AOB, Q&A & Adjourn

    • Citi to follow up on organisational goals and roadmap at the next meeting.
    • Next meeting agenda to be posted, and participants invited to add further topics/issues.

Action Items

  • @jescalada: Email help@finos.org regarding container registry and Docker image publication best practices; update the team.
  • @kriswest: Keep "checkUserPushPermission" refactor on agenda for post-2.0 and initiate technical solution discussion.
  • @grovesy: Draft and update roadmap for New workflow architecture #1383 (workflow/new architecture); clarify status and scope for next meeting.
  • @re-vlad: Improve and extend agents.md/AI policy file per Improve and standardize Agentic AI tooling #1410; ensure architectural context is included.
  • @jescalada: Document and standardise release/branching process in contributing.md for v2.1+; circulate for review.
  • @jescalada: Merge plugin imports PR (fix(plugins): update sample plugin imports to use package subpath exports #1484) after confirmation, then cut RC6 and notify team for testing.
  • @coopernetes: Confirm plugin fix works post-RC6, or report/patch if issues arise.
  • All: Test v2.0 RC6 as soon as available; report results and sign off for release.
  • All: Tag issues/PRs as candidates for 2.1 milestone ahead of next meeting.
  • @andypols & Zohar-melamed: Add redacted UI screenshots to appropriate issue or agenda for team review.
  • @kriswest: Document authentication/GCM issues in a new GitHub issue for team review.
  • Citi team: Bring organisational goals and priorities for GitProxy to next meeting; present or post as issue.

Activity

  1. kriswest
    added
    meeting
    on Mar 23, 2026

  2. re-vlad commented on Apr 5, 2026

    @re-vlad
    re-vlad
    on Apr 5, 2026
    Contributor

    Hi, @kriswest I'm a new contributor and I'd like to submit a PR. The contributing guide mentions that a CLA must be on file with FINOS before a PR can be merged. Could you clarify what the CLA process looks like? Is there an online form I can fill out, or does it require a physical signature?

  3. kriswest commented on Apr 10, 2026

    @kriswest
    kriswest
    on Apr 10, 2026
    ContributorAuthor

    Hi, @kriswest I'm a new contributor and I'd like to submit a PR. The contributing guide mentions that a CLA must be on file with FINOS before a PR can be merged. Could you clarify what the CLA process looks like? Is there an online form I can fill out, or does it require a physical signature?

    HI @re-vlad, we use EasyCLA to manage CLA signatures. If you raise PR (either for real or just open test PR that you subsequently close) it will process the email addresses found in the commits and try to find a CLA. If doesn't find one for each author email it will comment on the PR and give you a link to sign one and 'get authorized'.

    I think you can get it pre-signed by using the EasyCLA link. But the first time you raise a PR you will need to use the get authorized link for it to look it up - for subsequent PRs it'll just find it.

  4. kriswest commented on Apr 13, 2026

    @kriswest
    kriswest
    on Apr 13, 2026
    ContributorAuthor

    @coopernetes and @grovesy we'll pu together a summary of the organisational goals we got through in today's meeting, and will try to set aside some time in the next meeting (next week) in case you want to discuss your own. I'll aim to merge what we got (which were all compatible) into a set for the project to guide our roadmap.

    • @grovesy the architectural issues you've raised would probably add detail and might prompt discussion
    • @coopernetes I haven't had a chance to engage with your jGit-proxy post as yet - but I would assume theres some relationship to organisational goals - if not I we can set aside a separate slot to talk about that. Let me know if the next meeting makes sense, or whether there is anotehr that would be better for you.

    As a reminder: we were meeting out of sequence this week due to easter, our next meeting is next week.

  5. coopernetes commented on Apr 13, 2026

    @coopernetes
    coopernetes
    on Apr 13, 2026
    Contributor

    Hey folks, sorry I missed this (dropped off my calendar). Will touch base next week on the Slack post.

  6. kriswest commented on Apr 13, 2026

    @kriswest
    kriswest
    on Apr 13, 2026
    ContributorAuthor

    No worries @coopernetes - note that since we migrated to LF meetings, its best to make sure you've hit the Register for future meetings link as you'll get a new invite from that, and any changes we make (like deferring this meeting a week) you'll get an update for.

  7. andypols commented on Apr 13, 2026

    @andypols
    andypols
    on Apr 13, 2026
    Contributor

    Here are a few screenshots from the demo:

    The repositories page

    Image

    Add repository page

    Image

    The repository details page now shows activity:

    Image

  8. kriswest commented on Apr 14, 2026

    @kriswest
    kriswest
    on Apr 14, 2026
    ContributorAuthor

    Minutes and actions posted!

  9. kriswest commented on Apr 14, 2026

    @kriswest
    kriswest
    on Apr 14, 2026
    ContributorAuthor

    As discussed at the meeting, I fed the transcript to an LLM which came up the following set of goals for us to consider (this is purely a WIP to inspire conversation and should be updated once we've gathered further input from @coopernetes and @grovesy):

    Git Proxy Project Goals

    1. Reduce Friction for Open Source Contribution

    Enable engineers in regulated and enterprise environments to contribute to open source with minimal overhead by:

    • Streamlining onboarding of users, repositories, and reviewers.
    • Automating repetitive administrative tasks (e.g., project setup, reviewer assignment).
    • Integrating with organisational tooling, including AI agents and identity providers, to accelerate common workflows.

    2. Ensure Full Auditability and Compliance

    Provide a complete, auditable record of all open source activity, supporting regulatory and internal governance requirements by:

    • Recording all contributions, approvals, and rejections with full traceability.
    • Establishing a "golden path" for contribution that satisfies internal and external audit expectations.
    • Eliminating the need for off-network or unauditable activity by supporting the full contribution lifecycle within the platform.

    3. Support the Full Open Source Contribution Lifecycle

    Move beyond push-and-approve workflows to cover the broader set of interactions developers need, including:

    • Creating and reviewing pull/merge requests.
    • Raising and commenting on issues.
    • Syncing forks and managing upstream relationships.
    • Surfacing relevant context (e.g., commit summaries, file changes) to reviewers within the platform.

    4. Enable Supply Chain Security and Code Ingress Review

    Extend Git Proxy's role to support inbound code review and risk assessment by:

    • Allowing pre-ingress evaluation of upstream changes, dependencies, and version updates.
    • Integrating with supply chain security tooling to surface risk signals before code enters the organisation.
    • Supporting approval workflows for ingress alongside existing egress controls.

    5. Deliver a Modern, Intuitive User Experience

    Provide a UI that reduces friction and encourages adoption by:

    • Presenting relevant information (pending reviews, recent activity) prominently and contextually.
    • Supporting flexible administration, including user and repository management, directly from the interface.
    • Ensuring responsive design and accessibility across devices.
    • Enabling plugins and extensions to contribute UI components where appropriate.

    6. Surface Contribution Metrics and Programme Health

    Help organisations understand and promote the impact of their open source programmes by:

    • Providing dashboards and summary views of contribution activity across repositories, users, and teams.
    • Supporting export or integration of metrics for internal reporting, programme health tracking, and volunteer matching.

    7. Maintain Extensibility and Forge Interoperability

    Ensure Git Proxy remains adaptable to diverse organisational needs and platforms by:

    • Maintaining a forge-agnostic core architecture, with initial focus on GitHub and clear extension points for GitLab, Bitbucket, and others.
    • Supporting plugin and configuration-driven customisation for notifications, workflows, and integrations.
    • Designing new features in a way that avoids hard dependencies on a single forge's API.

    8. Grow and Support the Contributor Community

    Lower barriers to participation and broaden the project's contributor base by:

    • Maintaining well-described, well-tagged issues (including "good first issues") to support new and external contributors.
    • Providing clear documentation of processes, architecture, and contribution guidelines.
    • Welcoming contributions from students, community members, and participating organisations alike.

    Next Steps

    • Circulate these goals for review and feedback from all participating organisations.
    • Use the agreed goals to guide roadmap prioritisation and milestone planning.
    • Revisit and update goals periodically as organisational needs and the project evolve.
  10. kriswest
    pinned this issue on Apr 17, 2026
  11. kriswest
    closed this as completedon Apr 20, 2026
  12. jescalada
    unpinned this issue on Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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