8000 Project Activation - Git proxy · Issue #361 · finos/community · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Project Activation - Git proxy #361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
JamieSlome opened this issue May 6, 2025 · 8 comments
Open

Project Activation - Git proxy #361

JamieSlome opened this issue May 6, 2025 · 8 comments
Assignees
@eddie-knight
Labels
ready-for-toc The issue is ready for TOC review

Comments

@JamieSlome
Copy link
Member
JamieSlome commented May 6, 2025 •
edited by mindthegab
Loading

@finos/toc - Git Proxy maintainers are requesting activation

Activation

Virtually all FINOS hosted projects are expected to strive towards, and ultimately attain, Active status and the related badge. An active badge indicates to potential consumers that the project has reached a level of maturity, both functional and non-functional, that it is suitable for production use.

The Technical Oversight Committee approves lifecycle transitions following objective criteria detailed in the below checklist.

What does activation mean for the consumer?

✔️ The Project is high quality, mature from a codebase and community dynamics perspective.

🎯 The Project produces valuable releases to solve a useful business problem for our Community.

What does activation mean for the project team?

⭐ Glory in the Community

👀 📢 Increased visibility and positioning in FINOS web resources, marketing and Community building efforts like meetups, blog posts, etc.

Activation Checklist

Activation (promotion to Active State) How and Where Demonstrated
QUALITY & SECURITY
Development Process

The Project adopts best-of-breed standards of distributed software development, including but not limited to:

  • semantic versioning
  • tagging / branch protection
  • continuous integration ("CI") and continuous delivery ("CD") where applicable
Build & Release

The Project code/documentation release process automated or at lest well documented.

If code is published, publicly redistributed release binaries should be listed or referred to in the documentation (e.g. under the FINOS namespace in an artefact repository or package manager, e.g. NPM, Maven Central, etc.)
Security
  • The project has an OpenSSF "Passing" badge
  • Maintainers are familiar with the FINOS Security vulnerabilities responsible disclosure
  • An automated security scanning tool is enabled on the project (e.g. FINOS Security Scanning or WhiteSource)
    		•
    Documentation

    The README.md must include or reference up to date:

    • end user docs, including a description of the software, feature overview, installation & configuration instructions
    • developer docs, including links to other external systems (further docs, wiki, CI & validation tools, artefact repository, change log / history, etc.)
    • where possible badges (e.g. from shields.io) are encouraged
    • sample code explaining how to use the project, library, standard, SDK, etc.
    		 ✅
    DIVERSITY & VIABILITY
    Community Project has active participation from 2+ independent individuals and/or organizations; Ideally Project Team members who make contributions in connection with their employment are doing do as part of their regular job duties. ✅ Member Maintainers: Jamie Slome (@JamieSlome) - Citigroup, Thomas Cooper (@coopernetes) - Royal Bank of Canada, Miklos Sagi (@msagi) - ex-Natwest, Barclays. Member Contributors: Jack Kelly (@06kellyjac) - ControlPlane, Fabio Vincenzi (@fabiovincenzi), Juan Escalada (@jescalada), Denis Ćorić (@dcoric) - G-Research, Kris West (@kriswest) - NatWest, Sam Moorhouse (@sammoorhouse),Gideon Aryeteey (@tt-gideonaryeetey) - turntabl
    Project Team Project Team has/have demonstrated active involvement commitment to the open source project ✅
    License Project must not have dependencies which effectively restrict how the project may be distributed or deployed and must not depend on any proprietary third-party components for their core functionality. ✅
    Trademark Community is using a different established Project name or original contribution trademark is owned by FINOS. All Project related websites and assets are owned and hosted by FINOS. ✅
    ROADMAP & RESOURCES
    Progress Project has progressed against its public roadmap during incubation. ✅
    Versioning Project software is production grade and ready for large scale consumption. 1.0.0 version was released and announced it to the announce@ mailing list. ✅
    Roadmap Projects share and work to a public roadmap. ✅
    FINOS Support Project Team is largely self-sufficient, requiring minimal operational support from FINOS to govern and maintain the project. FINOS support switches to strategic growth of the Project in the Community. ✅
    GROWTH & ADOPTION
    Usefulness The Project demonstrably solves a real life use case in the Community. Evidence of adoption beyond the contributing individuals or firms (e.g., in the form of download statistics, listing known deployments or implementations, etc.) ✅
    Status Badging Project Team commits to adopt the FINOS Active badge in the README.md once the FINOS team approves activation, in order to properly signal the new Project Lifecycle status to adopters. ✅
    HYGIENE & OPERATIONS
    Compliance The appropriate license text is included in each source file's header. See details and template ⏳
    Community Inquiries Community inquiries on the project channels (mailing lists, issues and pull requests, etc) are generally promptly answered ✅
    Meeting Hygiene If the project meets regularly on-line, the Project Team has demonstrated a track record of publishing and distributing agenda no less than 24 hours before the meeting, and publishes meeting minutes after calls.
    Transparency Project Team has adopted a transparent governance model(*) consistent with FINOS Community governance. Work for new contributors is organized into issues within a public issue tracking system, as appropriate, tagged as "Good First Issues" ✅

    (*) transparent governance model is when a project’s discussions, minutes, deliberations, project plans, issue tracking plans for new features, and other artefacts are open, public, and easily accessible in the FINOS Project Infrastructure or FINOS sanctioned external system.
    @JamieSlome
    Copy link
    Member Author

    @mindthegab - et voila 🎉

    @JamieSlome JamieSlome mentioned this issue May 6, 2025
    Open
    2 tasks
    @mindthegab mindthegab changed the title Project Activation Project Activation - Git proxy May 6, 2025
    @mindthegab
    Copy link
    Member

    Hi @JamieSlome - thank you for this!

    Before we assign to the @finos/toc ( @eddie-knight @psmulovics FYI) for review, can I ask you to edit the issue providing some more details on:

    • Community - can you list maintainers and, if applicable, their affiliation?

    • Usefulness - I know git-proxy is used in multiple organizations (and in commercial products) so it would be good, to the extent it's not confidential, to post at least a number of known implementations.

    Thanks!

    @mindthegab
    Copy link
    Member

    Also tagging @coopernetes @kriswest to chime in as needed

    @JamieSlome
    Copy link
    Member Author

    Community

    Member Maintainers

    Jamie Slome (@JamieSlome) - Citigroup
    Thomas Cooper (@coopernetes) - Royal Bank of Canada
    Miklos Sagi (@msagi) - ex-Natwest, Barclays

    Member Contributors

    Jack Kelly (@06kellyjac) - ControlPlane
    Fabio Vincenzi (@fabiovincenzi), Juan Escalada (@jescalada), Denis Ćorić (@dcoric) - G-Research
    Kris West (@kriswest) - NatWest
    Sam Moorhouse (@sammoorhouse), Gideon Aryeteey (@tt-gideonaryeetey) - turntabl

    Usefulness

    @mindthegab - can we internally share the study with the TOC? This perfectly summarises the implementation for our members.

    @mindthegab
    Copy link
    Member

    Thanks @JamieSlome - that's perfect. I've edited the description to include the maintainers in the community section.

    Re case study - we should be close to publishing it at this stage (@grizzwolf @winmorgan) so once it's out, I'll link it here - definitely agreed it's the best proof point.

    @sammoorhouse
    Copy link

    Turntabl uses GitProxy widely internally. We have extended the tool with gh credential capture, a stack of plugins and a configuration UI. We are regular contributors to GitProxy and have upstreamed a number of features. We are proud to support the activation of the GitProxy project!

    @mindthegab mindthegab assigned 8000 eddie-knight and unassigned maoo and TheJuanAndOnly99 May 13, 2025
    @mindthegab mindthegab added the ready-for-toc The issue is ready for TOC review label May 13, 2025
    @mindthegab
    Copy link
    Member

    Hey @eddie-knight - assigned to you and added to the TOC backlog as the checklist seems pretty complete.

    I also shared on the TOC private list adoption information per case study currently confidential.

    Please let @JamieSlome know directly if you need more information.

    @eddie-knight eddie-knight moved this from 🆕 Suggestions to 🏗 In progress in FINOS Technical Oversight Committee Backlog May 14, 2025
    @eddie-knight eddie-knight moved this from 🏗 In progress to 📋 Prioritised backlog in FINOS Technical Oversight Committee Backlog May 14, 2025
    @mindthegab mindthegab mentioned this issue May 22, 2025
    Open
    15 tasks
    @eddie-knight
    Copy link
    Contributor

    Hey @JamieSlome — I've scheduled a TOC vote on this for next week so that the results will be finalized next Friday, June 6th.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees

    @eddie-knight eddie-knight

    Labels
    ready-for-toc The issue is ready for TOC review
    Projects
    FINOS Technical Oversight Committee Backlog
    Status: 📋 Prioritised backlog
    Milestone
    No milestone
    Development

    No branches or pull requests
    6 participants
    @maoo @sammoorhouse @mindthegab @eddie-knight @TheJuanAndOnly99 @JamieSlome
    0