diff --git a/.github/ISSUE_TEMPLATE/Special-Interest-Group-Contribution.md b/.github/ISSUE_TEMPLATE/Special-Interest-Group-Contribution.md deleted file mode 100644 index 62330c8e..00000000 --- a/.github/ISSUE_TEMPLATE/Special-Interest-Group-Contribution.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -name: "\U0001F58ASpecial Interest Group Contribution and Onboarding" -about: To Contribute a Special Interest Group to FINOS -title: Special Interest Group Contribution and Onboarding -labels: contribution -assignees: maoo, TheJuanAndOnly99 - ---- -Please note that only FINOS members can propose new projects. If you're interested in membership, see https://www.finos.org/membership-benefits#become-a-member. - -## Business Problem -*Describe the business problem the contribution solves* - -## Proposed Solution -*Describe the type of contribution and how it solves that business problem* - -## Current State -*Summarize the history and current state of the special interest group* - -## 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* - -## SIG Maintainers -*Who will be the [SIG maintainer(s)](https://community.finos.org/docs/finos-maintainers-cheatsheet/#maintainer-responsibilities-and-available-resources)? Provide full name, affiliation, work email address, and GitHub.com username.* - -# SIG Contribution and Onboarding process (v. 1.0, last updated on October 27, 2020) -Below is the list of tasks that FINOS Team and the contribution author goes through in order to complete the FINOS SIG onboarding process. **Please do not edit these contents at contribution time!** - -## Voting (SIG Lead and FINOS ED) -- [ ] Contribution author triggers community socialization to gauge interest - recommended emailing issue link to community@finos.org -- [ ] If there's positive response from the Community, prepare short SIG proposal deck for the FINOS Governing Board. You can start from [this template](/governance-docs/202103-New-Project-or-SIG-proposal-(template)-PUBLIC.pptx) or see a [previous SIG example](https://community.finos.org/assets/files/202101-InnerSource-SIG-Proposal-APPROVED-85e2fa26d6d2589ea59eb4ff6ab31e67.pdf) -- [ ] Assign issue to Executive Director (@mindthegab) to trigger vote -- [ ] Executive Director brings SIG to the Board for additional socialization and approval -- [ ] FINOS board accepts the SIG (and the onboarding process can move forward) - -## Identify project meta (Lead: FINOS SIG POC, Support: FINOS Marketing) -- [ ] Identify and Assign FINOS SIG POC -- [ ] Link to SIG approval resolution - // _public link to board resolution_ -- [ ] SIG Name - - [ ] Assess current trademark status - - [ ] Define new SIG name (if applicable) - - [ ] Design new SIG logo (if applicable) - - [ ] Trademark new SIG name and logo (if applicable) -- [ ] Category and sub-category (for FINOS Landscape) -- [ ] Existing content/assets or new Github repository -- [ ] Team composition: lead maintainer and other maintainers -- [ ] Meetings? (existing/yes/no) -- [ ] Meeting minutes, agenda, attendance tracking (existing/yes/no) -- [ ] Documentation website (existing/yes/no) -- [ ] Define SIG slug : Dependant on `Define new SIG name` - -## Project Communication Channel(s) -- [ ] Ask maintainers which communications channels they'd like to use and if more than one are needed. These may include - - [ ] Creation of one or more project mailing lists (e.g. general@, or dev@ and users@) - - [ ] Creation of one or more Slack or Symphony chats for the project -- [ ] Create the identified communication channels during infra set up -- [ ] Link communication channels linked front and center in the project README.md. - -## Repository transfer (Lead: FINOS Infra) -- [ ] Check GitHub repository transfer requirements: - - [ ] [finos-admin](http://github.com/finos-admin) has `Admin` to all repositories to transfer - - [ ] [finos-admin](http://github.com/finos-admin) is allowed to transfer repositories out of the org - - [ ] if the repository is owned by a user (and not an org), the user must be able to transfer the repository to [finos-admin](http://github.com/finos-admin) -- [ ] Transfer all assets as GitHub repositories under github.com/finos -- [ ] Invite GitHub usernames to GitHub FINOS Org -- [ ] Create `-maintainers` GitHub team and invite users -- [ ] Configure `finos-admins` and `finos-staff` team permissions - -## Infra setup (Lead: FINOS Infra) -- [ ] Update SIG badge -- [ ] Update SIG README -- [ ] Enable meeting attendance tracking (optional) - -## Metadata update (Lead: FINOS Infra) -- [ ] Add SIG to metadata -- [ ] Add identities, orgs and affiliations to metadata -- [ ] Add logo to FINOS landscape -- [ ] Add SIG Leads emails to finos-project-maintainers@finos.org list -- [ ] Add SIG Leads GitHub usernames to the project-maintainers Team - -## Update FINOS SIG Roster -- [ ] [FINOS Governance](https://community.finos.org/docs/governance/special-interest-groups) - -## Announcement (Lead: FINOS POC) -- [ ] Work with FINOS marketing to send out announcement to announce@finos.org , checkout announcement template at the [Contribution page](https://community.finos.org/docs/governance/Software-Projects/contribution). -- [ ] Notify FINOS POC and FINOS marketing manager once the announcement has been sent out (FINOS infra) - -## Press Release (OPTIONAL) (Lead: FINOS POC) -- [ ] Identify quotes for press release -- [ ] Draft press release -- [ ] Send embargoed press release to reporters -- [ ] Coordinate social media promotion of the press release with FINOS marketing - - [ ] Post on FINOS social media - - [ ] Post on LF social media - -## Onboarding and training -- [ ] FINOS SIG Governance -- [ ] FINOS Project Lifecycle -- [ ] FINOS Collaboration infrastructure - -## Contributors Metadata (Lead: FINOS SIG POC, Support: FINOS infra) -- [ ] For each SIG material contributor identified in the previous step, collect: the following info: - - Fullname - - GitHub username - - Corporate email address -- [ ] Identify other existing contributors (assuming there's a contribution history (eg Git history) diff --git a/.github/ISSUE_TEMPLATE/Standards-Project-Contribution.md b/.github/ISSUE_TEMPLATE/Standards-Project-Contribution.md deleted file mode 100644 index bc6520ff..00000000 --- a/.github/ISSUE_TEMPLATE/Standards-Project-Contribution.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -name: "\U0001F58AStandard Project Contribution and Onboarding" -about: To Contribute a Standard Project to FINOS -title: Standard Project Contribution and Onboarding -labels: contribution -assignees: maoo, TheJuanAndOnly99 - ---- -Please note that only FINOS members can propose new Standards projects. If you're interested in membership, see https://www.finos.org/membership-benefits#become-a-member. - -## Contribution Requirements — read this first - -**Before you submit this proposal**, read **[FINOS Contribution Requirements](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements)**. It covers how new contributions are licensed (including CSLA for standards vs DCO/CLA for software), notice files, and third-party rules. - - -**Standards** projects follow the [FINOS Standards Project Blueprint](https://github.com/finos/standards-project-blueprint) for Community Specification license, CSLA, and related governance documents—use the blueprint’s filenames and layout for standards work. - -## Business Problem -*Describe the business problem or opportunity the proposed standard addresses* - -## Proposed Solution -*Describe the proposed standard, including the format if known (e.g. specification, model, extension to existing standard) and how it solves that business problem* - -## Tentative Roadmap -*Describe the short and medium term goals and phases of the project. What does success look like for this project?* - -## Scope -*Clearly define the scope of the standard. In cases where the scope is expected to be defined by the standard project participants this should be one of the first tasks the group completes. Guidelines can be found in the [Community Specification documentation](https://github.com/finos/standards-project-blueprint).* - -## 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 repository, you should invite the finos-admin user with R/O permissions to those repositories* - -## Development Team - -### Maintainers -*Who will be the [project maintainer(s)](https://community.finos.org/docs/finos-maintainers-cheatsheet/#maintainer-responsibilities-and-available-resources)? Provide full name, affiliation, work email address, and GitHub.com 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* - -## Infrastructure needs -*Describe the FINOS infrastructure you will need for this project, in addition to a GitHub repository. The FINOS team will connect with you before setting up any of this infrastructure* -- [ ] Recurring meetings -- [ ] Mailing list -- [ ] A project on the [Legend Studio shared instance](https://community.finos.org/docs/platforms/legend-studio-shared) -- [ ] Other (please explain): - -# What's next? -Upon submission of this project proposal, the FINOS team will get in touch with you to discuss next steps. - ------ - -# Contribution process (v. 1.0, last updated on May 26, 2021) -Below is the list of tasks that FINOS Team and the contribution author go through in order to complete the FINOS contribution process. -**Please do not edit these contents at contribution time!** - -## FINOS Contrib POC -- [ ] Identify and Assign FINOS Contrib POC - -## Kick-off meeting -- [ ] Set up kick-off meeting with project leads to cover - - [ ] [FINOS overview](https://www.finos.org/hubfs/An%20Introduction%20to%20FINOS.pdf) (if necessary) - - [ ] [FINOS Maintainers cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet/) - - [ ] Discuss project proposal - -## Proposal (Lead Maintainer) -- [ ] Lead maintainer to send out announcement to community@finos.org using this template: - - ``` - Dear FINOS Community, - - We would like to propose a new FINOS project. Please review the proposal details at (_TODO: add link to the GitHub issue proposal_). - - If you're interested in participating, please :+1: the GitHub issue proposal and drop a comment with your name, org and email - - Thanks a lot, - ``` - -## Identify project meta (Lead: FINOS Contrib POC, Support: FINOS Marketing) -- [ ] Project Name - - [ ] Standard Name - - [ ] Assess current trademark status - - [ ] Define new project name (if applicable) - - [ ] Design new project logo (if applicable) - - [ ] Trademark new project name and logo (if applicable) -- [ ] Category and sub-category (for FINOS Landscape) -- [ ] Existing code or new Github repository -- [ ] Existing code releases (and which artifact repositories are used) -- [ ] Team composition: lead maintainer and other maintainers -- [ ] Meetings (existing/yes/no) -- [ ] Meeting minutes, agenda, attendance tracking (existing/yes/no) -- [ ] Continuous Integration (existing/yes/no) -- [ ] Documentation website (existing/yes/no) -- [ ] Define project slug - -## Maintainers, contributors and CLAs (Lead: FINOS Contrib POC, Support: FINOS infra) -- [ ] For each maintainer identified in the previous step, collect: the following info: - - Fullname - - GitHub username - - Corporate email address -- [ ] Identify other existing contributors (assuming there's a contribution history (eg Git history) -- [ ] Maintainers to determine if participants will be required to execute a Community Specification License Agreement (CSLA) or submit a Pull Request to accept the license terms. -- [ ] (optional) Check if maintainers, editors, and other participants are covered by a FINOS CSLA - -## Project Communication Channel(s) -- [ ] Ask maintainers which communications channels they'd like to use -- Asynchronous - - [ ] GitHub Issues (_public_) - - [ ] GitHub Discussions (_public_) - - [ ] GitHub Team Discussions (_public_ and _private_ **FINOS CLAs Required**) - - [ ] Google Groups or Groups.io -- Synchronous - - [ ] FINOS Slack Channel (general _public Slack_ / leadership _private Slack_) -- [ ] Create the identified communication channels during infra set up -- [ ] Link communication channels linked front and center in the project README.md - -## Approval (Lead: FINOS Infra) -- [ ] Assign issue to Executive Director (@mindthegab) to trigger voting - (optional). If additional socialization is required, the Executive Director may bring standards projects to the FINOS Governing Board -- [ ] FINOS accepts the contribution/new standard project (and the contribution process can move forward) - -## Assets transfer (optional - Lead: FINOS Infra) -- [ ] Check GitHub repository transfer requirements: - - [ ] [finos-admin](http://github.com/finos-admin) has `Admin` to all repositories to transfer - - [ ] [finos-admin](http://github.com/finos-admin) ia allowed to transfer repositories out of the org - - [ ] if the repository is owned by a user (and not an org), the user must be able to transfer the repository to [finos-admin](http://github.com/finos-admin) -- [ ] Transfer all code assets as GitHub repositories under github.com/finos -- [ ] Invite GitHub usernames to GitHub FINOS Org -- [ ] Create `-maintainers` GitHub team and invite users -- [ ] Configure `finos-admins` and `finos-staff` team permissions - -## Infra setup (Lead: FINOS Infra) -- [ ] Update release coordinates and code namespace to include `finos` (best effort) -- [ ] Update project badge -- [ ] Update project README -- [ ] Aggregate mailing lists to community@finos.org -- [ ] Enable meeting attendance tracking (optional) -- [ ] (optional) Onboard into legend.finos.org/studio - -## Metadata update (Lead: FINOS Infra) -- [ ] Add project to metadata -- [ ] Add identities, orgs and affiliations to metadata -- [ ] Add logo to FINOS landscape -- [ ] Add maintainers emails to finos-project-maintainers@finos.org list -- [ ] Add maintainers GitHub usernames to the project-maintainers Team -- [ ] Onboard project on LF systems ([SFDC](https://jira.linuxfoundation.org/browse/SOPS), Insights, EasyCLA, Groups.io) - -## Mailing list (optional) -- [ ] Create mailing-list -- [ ] Enable Hubspot Sync for all project mailing lists created -- [ ] Update marketing lists - - Add new list to the included "Email List" part of the filter - - Add new list to the excluded "Email" part of the filter -## Announcement (Lead: FINOS Contrib POC) -- [ ] Work with FINOS marketing to send out announcement to announce@finos.org , checkout announcement template at the [Contribution page](https://community.finos.org/docs/governance/Software-Projects/contribution). -- [ ] Notify FINOS Contrib POC and FINOS marketing manager once the announcement has been sent out (FINOS infra) - -## Marketing collateral and Social (Lead: FINOS Marketing) -- [ ] Update FINOS marketing collaterals to update numbers and include the new project -- [ ] Post on FINOS social media -- [ ] Post on LF social media -- [ ] Email brief announcement to lf_staff@linuxfoundation.org (Optional depending applicability of contribution) - -## Onboarding and training (Lead: FINOS Infra) -- [ ] FINOS Standards Project Governance -- [ ] FINOS Standards Project Lifecycle - -## Press Release (OPTIONAL - Lead: FINOS Marketing) -- [ ] Identify quotes for press release -- [ ] Draft press release -- [ ] Send embargoed press release to reporters diff --git a/.github/ISSUE_TEMPLATE/special_interest_group_contribution.yml b/.github/ISSUE_TEMPLATE/special_interest_group_contribution.yml new file mode 100644 index 00000000..a9472ea4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/special_interest_group_contribution.yml @@ -0,0 +1,148 @@ +name: "📣 Special Interest Group Contribution" +description: "Propose a new FINOS Special Interest Group (SIG)." +title: "Proposed SIG: [SIG Name]" +labels: ["contribution"] +assignees: ["maoo", "TheJuanAndOnly99"] +body: + - type: markdown + attributes: + value: | + ### Welcome to the FINOS Community! + Thank you for your interest in proposing a FINOS Special Interest Group. Please complete all required fields so the FINOS team can process your proposal efficiently. + + #### ⚠️ Important Note on Membership + Only **FINOS members** can propose new SIGs. [See here](https://www.finos.org/membership-benefits#become-a-member) if you are interested in becoming a FINOS member. + + - type: checkboxes + id: prerequisites + attributes: + label: Contribution Prerequisites + options: + - label: "I confirm I am proposing this SIG on behalf of a FINOS member." + required: true + - label: "I have reviewed [Special Interest Groups governance](https://community.finos.org/docs/governance/#special-interest-groups)." + required: true + - label: "I have reviewed the [FINOS Project Lifecycle](https://community.finos.org/docs/governance/project-lifecycle) stages." + required: true + - label: "I am familiar with [FINOS Governance](https://community.finos.org/docs/governance) and [Maintainer Responsibilities](https://community.finos.org/docs/finos-maintainers-cheatsheet/)." + required: true + + - type: input + id: member_org_name + attributes: + label: FINOS Member Organization Name + description: "Enter the member organization backing this proposal." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: markdown + attributes: + value: "## SIG Details" + + - type: input + id: sig_name + attributes: + label: Name + placeholder: "The proposed SIG name" + validations: + required: true + + - type: input + id: sig_slug + attributes: + label: Slug + description: "Must be kebab-case (e.g., my-sig-name)" + validations: + required: true + + - type: textarea + id: business_problem + attributes: + label: Business Problem + description: "Describe the business problem or community need this SIG addresses." + validations: + required: true + + - type: textarea + id: proposed_solution + attributes: + label: Proposed Solution + description: "Describe the SIG's purpose, expected discussions, outputs, and how it addresses the business problem." + validations: + required: true + + - type: textarea + id: current_state + attributes: + label: Current State + description: "Summarize the history and current state of this effort, including any existing informal working group or community interest." + validations: + required: true + + - type: textarea + id: existing_materials + attributes: + label: Existing Materials + description: "Provide links to existing materials. If private, grant read access to 'finos-admin'." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: markdown + attributes: + value: "## Team" + + - type: textarea + id: sig_chair_and_maintainers + attributes: + label: Proposed SIG Chair and Maintainers + description: "Provide the initial SIG chair and co-chair and other maintainers with full name, affiliation, work email, and GitHub username." + value: | + | Role | Name | Affiliation | Email | GitHub Username | + | :--- | :--- | :--- | :--- | :--- | + | Chair | | | | | + | Co-Chair | | | | | + validations: + required: true + + - type: textarea + id: target_participants + attributes: + label: Target Participants + description: "Describe the participant profile you want to attract (background, role, organization type)." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: checkboxes + id: compliance_confirmation + attributes: + label: Governance & Policy Acknowledgements + description: "Confirm you understand the following SIG requirements." + options: + - label: "I understand new SIGs are proposed by FINOS members and approved by the FINOS Governing Board" + required: true + - label: "I understand documents produced or contributed as part of the SIG will be made available under the CC-BY-4.0 license" + required: true + - label: "I understand the SIG and it's participants must comply with all [FINOS policies](https://community.finos.org/docs/governance/#policies)." + required: true + - label: "I understand this proposal may require socialization via community@finos.org before final review." + required: true + + - type: markdown + attributes: + value: | + ### What's Next? + After you submit this proposal, the FINOS team will follow up with next steps for review and socialization. New SIGs are approved by the FINOS Governing Board. + + If there's positive response from the community, prepare a short SIG proposal deck for the FINOS Governing Board. You can start by downloading and using [this template](https://github.com/finos/community/raw/refs/heads/main/website/static/governance-docs/202103-New-Project-or-SIG-proposal-(template)-PUBLIC.pptx). See a [previous SIG example](https://community.finos.org/assets/files/202101-InnerSource-SIG-Proposal-APPROVED-85e2fa26d6d2589ea59eb4ff6ab31e67.pdf). diff --git a/.github/ISSUE_TEMPLATE/standards_project_contribution.yml b/.github/ISSUE_TEMPLATE/standards_project_contribution.yml new file mode 100644 index 00000000..f800d965 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/standards_project_contribution.yml @@ -0,0 +1,178 @@ +name: "📜 Standard Project Contribution" +description: "Propose a new FINOS Standards Project." +title: "Proposed Standard: [Standard Name]" +labels: ["contribution"] +assignees: ["maoo", "TheJuanAndOnly99"] +body: + - type: markdown + attributes: + value: | + ### Welcome to the FINOS Community! + Thank you for your interest in contributing an FINOS Standard Project. Please complete all required fields so the FINOS team can process your proposal efficiently. + + #### ⚠️ Important Note on Membership + Only **FINOS members** can propose new standards projects. Non-members are encouraged to identify a member sponsor during socialization. [See here](https://www.finos.org/membership-benefits#become-a-member) if you are interested in becoming a FINOS member. + + - type: checkboxes + id: prerequisites + attributes: + label: Contribution Prerequisites + options: + - label: "I confirm I am contributing on behalf of a FINOS member OR I will seek a maintainer from a member during socialization." + required: true + - label: "I have reviewed [Open Standard Projects governance](https://community.finos.org/docs/governance/#open-standard-projects)." + required: true + - label: "I have reviewed [Establishing and Running an Open Standard project](https://community.finos.org/docs/governance/standards-projects/)." + required: true + - label: "I have reviewed the [FINOS Project Lifecycle](https://community.finos.org/docs/governance/project-lifecycle) stages." + required: true + - label: "I am familiar with [FINOS Governance](https://community.finos.org/docs/governance) and [Maintainer Responsibilities](https://community.finos.org/docs/finos-maintainers-cheatsheet/)." + required: true + - label: "I have reviewed the [FINOS Contribution Requirements](https://community.finos.org/docs/governance/software-projects/contribution-compliance-requirements/) and understand the intellectual property and licensing expectations for standards projects" + required: true + + - type: input + id: member_org_name + attributes: + label: FINOS Member Organization Name + description: "Enter the member organization backing this proposal." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: markdown + attributes: + value: "## Standard Details" + + - type: input + id: standard_name + attributes: + label: Name + placeholder: "The proposed standard common name" + validations: + required: true + + - type: input + id: standard_slug + attributes: + label: Slug + description: "Must be kebab-case (e.g., my-standard-name)" + validations: + required: true + + - type: textarea + id: business_problem + attributes: + label: Business Problem + description: "Describe the business problem or opportunity this proposed standard addresses." + validations: + required: true + + - type: textarea + id: proposed_solution + attributes: + label: Proposed Solution + description: "Describe the proposed standard (for example, specification, model, or extension to existing standard) and how it solves the business problem." + validations: + required: true + + - type: textarea + id: tentative_roadmap + attributes: + label: Tentative Roadmap + description: "Describe short- and medium-term goals, phases, and what success looks like." + validations: + required: true + + - type: textarea + id: scope + attributes: + label: Scope + description: "Define the scope of the standard. In cases where the scope is expected to be defined by the standard project participants this should be one of the first tasks the group completes. Guidelines can be found in the [Community Specification documentation](https://github.com/finos/standards-project-blueprint)." + validations: + required: true + + - type: textarea + id: current_state + attributes: + label: Current State + description: "Summarize the history and current state of the project." + validations: + required: true + + - type: textarea + id: existing_materials + attributes: + label: Existing Materials + description: "Provide links to existing materials. If private, grant read access to 'finos-admin'." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: markdown + attributes: + value: "## Team" + + - type: textarea + id: maintainers + attributes: + label: Maintainers + description: "Provide maintainers with full name, affiliation, work email, and GitHub username." + value: | + | Name | Affiliation | Email | GitHub Username | + | :--- | :--- | :--- | :--- | + | John Doe | Example LTD | john@example.com | @johnexampleabc | + | Jane Doe | Example LTD | jane@example.com | @janeexamplexyz | + validations: + required: true + + - type: textarea + id: confirmed_participants + attributes: + label: Confirmed Participants + description: "List participants committed or interested in contributing (full name, affiliation, work email, GitHub username). A **Participant** is anyone who either submits a contribution to the project (including code, issues, comments, documentation, media, or any combination of the above) or actively engages in online meetings and supports the adoption of the standard." + + - type: textarea + id: target_participants + attributes: + label: Target Participants + description: "Describe the participant profile you want to attract (background, role, organization type)." + validations: + required: true + + - type: markdown + attributes: + value: "---" + + - type: checkboxes + id: compliance_confirmation + attributes: + label: Compliance & Requirements Agreement + description: "Confirm you have read and agree to the standards governance and IP requirements." + options: + - label: "I understand standards projects follow the [Community Specification process](https://community.finos.org/docs/governance/standards-projects/) and should use the [FINOS Standards Project Blueprint](https://github.com/finos/standards-project-blueprint)." + required: true + - label: "I understand the [IP licensing requirements](https://community.finos.org/docs/governance/standards-projects/#ip-licensing-requirements), including that all participants must agree to the CSLA." + required: true + - label: "I understand the [patent exclusion rules](https://community.finos.org/docs/governance/standards-projects/#community-specification-license-patent-exclusion-rules) in the Community Specification License process." + required: true + - label: "I understand any software included in this standards project must follow FINOS software licensing rules (Apache-2.0 unless otherwise approved)." + required: true + - label: "I understand the standard project and it's participants must comply with all [FINOS policies](https://community.finos.org/docs/governance/#policies)." + required: true + - label: "I understand new open standard projects are approved by the FINOS Governing Board." + required: true + - label: "I understand this proposal may require socialization with community@finos.org before final review." + required: true + + - type: markdown + attributes: + value: | + ### What's Next? + After you submit this proposal, the FINOS team will follow up with next steps for review, socialization and approval. New open standards projects are approved by the FINOS Governing Board. diff --git a/docs/governance/Software-Projects/Contribution.md b/docs/governance/Software-Projects/Contribution.md index 0a8d26d4..0a18451e 100644 --- a/docs/governance/Software-Projects/Contribution.md +++ b/docs/governance/Software-Projects/Contribution.md @@ -44,8 +44,8 @@ By default, a new software project contribution enters FINOS at the **[Labs](/do Draft a proposal to be reviewed by the FINOS team. Please use the available templates for: - [Open source software project](https://github.com/finos/community/issues/new?template=software_project_contribution.yml) -- [Open standard / specification project](https://github.com/finos/community/issues/new?assignees=TheJuanAndOnly99%2C+maoo&labels=contribution&template=Standards-Project-Contribution.md&title=%3Cinsert%20name%20here%3E+Standard+Project+Contribution+and+Onboarding) -- [Special Interest Group](https://github.com/finos/community/issues/new?assignees=TheJuanAndOnly99%2C+maoo&labels=contribution&template=Special-Interest-Group-Contribution.md&title=%3Cinsert%20name%20here%3E+SIG+Contribution+and+Onboarding) +- [Open standard / specification project](https://github.com/finos/community/issues/new?template=standards_project_contribution.yml) +- [Special Interest Group](https://github.com/finos/community/issues/new?template=special_interest_group_contribution.yml) This will create a new issue on the [FINOS Community Repository](https://github.com/finos/community/issues) and kick off the process. The proposal is meant to cover the following: