-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
openGRIS - Software Project Contribution and Onboarding #326
Comments
I met with @bansalr to discuss the contribution. Couple of items I asked for:
I also suggested meeting with other member firms to assess interest within the community. |
@finos/toc @eddie-knight can we please clarify if this is a software or a standard project? If a standard project, per current contribution process, it should go to the Board for approval vs the TOC. |
Yes, @mindthegab that's correct. @bansalr — If you'd like to convert this into a standards proposal, @TheJuanAndOnly99 has offered to assist. |
1. Describing The Contribution
Business Problem
Describe the business problem the contribution solves
Large financial organizations have a heterogenous and distributed compute resources - physical severs, virtual instances, cloud compute (AWS, GCP, ....) and proprietary grids. There are multiple challenges around utilizing these efficiently. Many grids runs at 30% or below utilization and worsens climate impact.
Proposed Solution
Describe the type of contribution (project or working group) and how it solves that business problem
openGRIS is an open Standard for Grid Resource Scheduling with client and worker standards to tie resources together and share them in a cost-effective and climate friendly way.
Tentative Roadmap
Describe the short and medium term goals and phases of the project. What does success look like for this project?
Proposal Standard (V1.0 - Done
Reference Implementation for Python - Done
RFC & Formalize Standard
Interfaces to existing grids - AWS, IBM Symphony
Multi-language bindings
Time Scheduling
Multi-Environment support via Docker/Podman
Current State
Summarize the history and current state of the project
Existing Materials
If materials already exist, provide a link to them that Foundation staff can access - if it's in a private GitHub.com repositories, you should invite the finos-admin user with R/O permissions to those repositories
Development Team
Maintainers
Who will be the project maintainer(s)? Provide full name, affiliation, work email address, and GitHub / GitLab username.
Confirmed contributors
If applicable, list all of the individuals that have expressed interest in and/or are committed to contributing to this project, including full name, affiliation, work email address, and GitHub.com username
Target Contributors
Describe the contributor profile (background, position, organization) you would like to get contributions from.
Engineers at Financial Institutions and software and hardware vendors (AWS, IBM, Google, HP, etc.)
Project Communication Channel(s)
Understanding FINOS Onboarding Requirements
As a project onboarding into FINOS, you will need to familiarize yourself and your contributor team with the following materials:
Record The Contribution (FINOS Infra)
2. Approval
The FINOS Technical Oversight Committee (TOC) is responsible for approving FINOS project contributions; feel free to check their contribution principles.
If needed, the TOC will request a follow up either via GitHub Issue comments or by inviting project leads to one of their recurrent meetings.
Tasks (for FINOS Infra/TOC)
ready-for-tsc
labelTOC Findings / Report
TOC to enter findings summary here.
3. Preparing For Onboarding
Before the FINOS team can onboard your project, there are a few housekeeping that need to be taken care of. These must be completed by the contributor, with help if required from the FINOS Infra.
Kick-off meeting
Proposal (Lead Maintainer)
Lead maintainer to send out announcement to community@finos.org using this template:
Logo / Trademarks
help@finos.org
(if needed)FINOS Project Blueprint
CONTRIBUTING.md
LICENSE
(replace{}
placeholders)Add documentation here
4. FINOS Onboarding
This is performed by FINOS Infra once the three previous stages are complete, with support from the contributor and the FINOS Infra team.
Maintainers, Contributors and CLAs
<project-name>-maintainers
GitHub team and invite usersValidation (only if code is contributed)
Admin
to all repositories to transferCode transfer
main
(instead ofmaster
)finos-admins
(Maintain
role) andfinos-staff
(Triage
role) team permissionsProject Communication Channel(s)
Email List
andEmail
filter fields), particularly Hubspot all community listRepository setup
staging
branch onfinos/finos-landscape
finos/metadata
changes on master (will udpdatelandscape.yml
infinos/finos-landscape
)staging
branch onfinos/finos-landscape
finos
Require a pull request before merging
)5. Announcement
(Lead: Project Lead and FINOS Infra team)
The text was updated successfully, but these errors were encountered: