diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md index fc9bcda0..7feeee49 100644 --- a/.github/CODE_OF_CONDUCT.md +++ b/.github/CODE_OF_CONDUCT.md @@ -1,3 +1,4 @@ # Code of Conduct for {project name} -Please see the [Community Code of Conduct](https://www.finos.org/code-of-conduct). +Please see the +[Community Code of Conduct](https://www.finos.org/code-of-conduct). diff --git a/.github/ISSUE_TEMPLATE/Bug_report.md b/.github/ISSUE_TEMPLATE/Bug_report.md index 32598229..e5be85eb 100644 --- a/.github/ISSUE_TEMPLATE/Bug_report.md +++ b/.github/ISSUE_TEMPLATE/Bug_report.md @@ -1,24 +1,32 @@ --- name: 🐛 Bug Report about: If something isn't working as expected 🤔. - --- ## Bug Report ### Steps to Reproduce: - 1. ...step 1 description... - 2. ...step 2 description... - 3. ...step 3 description... + +1. ...step 1 description... +2. ...step 2 description... +3. ...step 3 description... ### Expected Result: + ...description of what you expected to see... ### Actual Result: -...what actually happened, including full exceptions (please include the entire stack trace, including "caused by" entries), log entries, screen shots etc. where appropriate... + +...what actually happened, including full exceptions (please include the entire +stack trace, including "caused by" entries), log entries, screen shots etc. +where appropriate... ### Environment: -...version and build of the project, OS and runtime versions, virtualised environment (if any), etc. ... + +...version and build of the project, OS and runtime versions, virtualised +environment (if any), etc. ... ### Additional Context: -...add any other context about the problem here. If applicable, add screenshots to help explain... + +...add any other context about the problem here. If applicable, add screenshots +to help explain... diff --git a/.github/ISSUE_TEMPLATE/Feature_request.md b/.github/ISSUE_TEMPLATE/Feature_request.md index b01f152f..325f6eb9 100644 --- a/.github/ISSUE_TEMPLATE/Feature_request.md +++ b/.github/ISSUE_TEMPLATE/Feature_request.md @@ -1,17 +1,22 @@ --- name: 🚀 Feature Request about: I have a suggestion (and may want to implement it 🙂)! - --- ## Feature Request ### Description of Problem: -...what *problem* are you trying to solve that the project doesn't currently solve? -...please resist the temptation to describe your request in terms of a solution. Job Story form ("When [triggering condition], I want to [motivation/goal], so I can [outcome].") can help ensure you're expressing a problem statement. +...what _problem_ are you trying to solve that the project doesn't currently +solve? + +...please resist the temptation to describe your request in terms of a solution. +Job Story form ("When [triggering condition], I want to [motivation/goal], so I +can [outcome].") can help ensure you're expressing a problem statement. ### Potential Solutions: -...clearly and concisely describe what you want to happen. Add any considered drawbacks. + +...clearly and concisely describe what you want to happen. Add any considered +drawbacks. ... if you've considered alternatives, clearly and concisely describe those too. diff --git a/.github/ISSUE_TEMPLATE/Support_question.md b/.github/ISSUE_TEMPLATE/Support_question.md index c6c4deb3..12ff4c48 100644 --- a/.github/ISSUE_TEMPLATE/Support_question.md +++ b/.github/ISSUE_TEMPLATE/Support_question.md @@ -1,11 +1,11 @@ --- name: 🤗 Support Question about: If you have a question about configuration, usage, etc. 💬 - --- ## Support Question ...ask your question here. -...be sure to search existing issues since someone might have already asked something similar. +...be sure to search existing issues since someone might have already asked +something similar. diff --git a/.github/ISSUE_TEMPLATE/meeting-minutes.md b/.github/ISSUE_TEMPLATE/meeting-minutes.md index 89358004..118e1799 100644 --- a/.github/ISSUE_TEMPLATE/meeting-minutes.md +++ b/.github/ISSUE_TEMPLATE/meeting-minutes.md @@ -3,59 +3,85 @@ name: "\U0001F91D InnerSource SIG Meeting Agenda and Minutes" about: To track InnerSource SIG meeting agenda and attendance title: DD MMM YYYY - InnerSource SIG Meeting Minutes labels: meeting -assignees: - +assignees: --- +## Date - ## Date _Monday_ DD MMM yyyy - _9:00am_ EST / _2:00pm_ UK ## Attendee Identity -Please identify yourself when you attend the meeting by providing your name and affiliation in reply to this thread. Alternative we will need to add you here if you do not have a Github id + +Please identify yourself when you attend the meeting by providing your name and +affiliation in reply to this thread. Alternative we will need to add you here if +you do not have a Github id + - Fullname, Affiliation, (optional) GitHub username - ... ## Meeting notices -- FINOS **SIG Leads** are responsible for observing the FINOS guidelines for [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/). - -- **All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://www.finos.org/code-of-conduct) and all other [FINOS policies](https://community.finos.org/docs/governance/#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 SIG 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. +- FINOS **SIG Leads** are responsible for observing the FINOS guidelines for + [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). + Project maintainers can find additional resources in the + [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/). + +- **All participants** in FINOS project meetings are subject to the + [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the + [FINOS Community Code of Conduct](https://www.finos.org/code-of-conduct) and + all other + [FINOS policies](https://community.finos.org/docs/governance/#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 SIG 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 + - [ ] Convene & roll call (5mins) -- [ ] Display [FINOS Antitrust Policy summary slide](https://www.linuxfoundation.org/legal/antitrust-policy) -- [ ] [Project Plan](https://github.com/orgs/finos/projects/104) Status -Review - - [ ] Review [InnerSource Repo Pull Requests](https://github.com/finos/InnerSource/pulls) - - [ ] Review [OSR InnerSource Site Pull Requests]([ -](https://github.com/finos/open-source-readiness/pulls?q=is%3Apr+is%3Aopen+label%3Ainnersource) +- [ ] Display + [FINOS Antitrust Policy summary slide](https://www.linuxfoundation.org/legal/antitrust-policy) +- [ ] [Project Plan](https://github.com/orgs/finos/projects/104) Status Review + - [ ] Review + [InnerSource Repo Pull Requests](https://github.com/finos/InnerSource/pulls) + - [ ] Review [OSR InnerSource Site Pull + Requests]([ ](https://github.com/finos/open-source-readiness/pulls?q=is%3Apr+is%3Aopen+label%3Ainnersource) - [ ] Agenda item 1 - [ ] Agenda item 2 - [ ] ... - [ ] AOB, Q&A & Adjourn (5mins) ## Decisions Made + - [ ] Decision 1 - [ ] Decision 2 - [ ] ... ## Zoom Minutes -- + +- ## Action Items + - [ ] Action 1 - [ ] Action 2 - [ ] ... ### Zoom Details -- [https://zoom-lfx.platform.linuxfoundation.org/meeting/92852768369?password=9ffd3106-34d9-42bc-b530-8c7866386826](https://zoom-lfx.platform.linuxfoundation.org/meeting/92852768369?password=9ffd3106-34d9-42bc-b530-8c7866386826) (please join with this link to register your attendance) +- [https://zoom-lfx.platform.linuxfoundation.org/meeting/92852768369?password=9ffd3106-34d9-42bc-b530-8c7866386826](https://zoom-lfx.platform.linuxfoundation.org/meeting/92852768369?password=9ffd3106-34d9-42bc-b530-8c7866386826) + (please join with this link to register your attendance) ### Join by phone + Find your local number: https://zoom.us/u/adJnH9JOiY ### Mailing List diff --git a/.github/ISSUE_TEMPLATE/working-group-minutes.md b/.github/ISSUE_TEMPLATE/working-group-minutes.md index df175761..71f7df5b 100644 --- a/.github/ISSUE_TEMPLATE/working-group-minutes.md +++ b/.github/ISSUE_TEMPLATE/working-group-minutes.md @@ -1,6 +1,7 @@ --- name: "\U0001F91D InnerSource SIG License Working Group Agenda and Minutes" -about: To track InnerSource SIG License Working Group meeting agenda and attendance +about: + To track InnerSource SIG License Working Group meeting agenda and attendance title: DD MMM YYYY - InnerSource SIG License Working Group Meeting Minutes labels: meeting assignees: @@ -17,13 +18,28 @@ _Monday_ DD MMM yyyy - _time_ EST / _time_ UK ## Meeting notices -- FINOS **SIG Leads** are responsible for observing the FINOS guidelines for [running project meetings](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md#run-the-meeting). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/). - -- **All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://github.com/finos/community/blob/master/governance/Code-of-Conduct.md) and all other [FINOS policies](https://github.com/finos/community/tree/master/governance#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 SIG 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. +- FINOS **SIG Leads** are responsible for observing the FINOS guidelines for + [running project meetings](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md#run-the-meeting). + Project maintainers can find additional resources in the + [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/). + +- **All participants** in FINOS project meetings are subject to the + [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the + [FINOS Community Code of Conduct](https://github.com/finos/community/blob/master/governance/Code-of-Conduct.md) + and all other + [FINOS policies](https://github.com/finos/community/tree/master/governance#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 SIG 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 @@ -56,6 +72,7 @@ _Monday_ DD MMM yyyy - _time_ EST / _time_ UK - Passcode: 878599 ### Join by phone + Find your local number: https://zoom.us/u/adJnH9JOiY ### Mailing List diff --git a/MAINTAINERS.md b/MAINTAINERS.md index a5dcfc87..2daaffc7 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -4,19 +4,22 @@ This file lists the maintainers of this repository. ## Current maintainers -| GitHub Username | Name | Organization | Email | -|----------------|------|--------------|-------| -| @chamindra | Chamindra de Silva | Citi | chamindra.desilva@citi.com | -| @pooi-cheong | Pooi Cheong | NatWest Group | pooiling.cheong@natwest.com | +| GitHub Username | Name | Organization | Email | +| --------------- | ------------------ | ------------- | --------------------------- | +| @chamindra | Chamindra de Silva | Citi | chamindra.desilva@citi.com | +| @pooi-cheong | Pooi Cheong | NatWest Group | pooiling.cheong@natwest.com | -For information about maintainer responsibilities and resources, see the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet). +For information about maintainer responsibilities and resources, see the +[FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet). ## Updating this file All changes to the maintainer list are managed openly: - **Submit a Pull Request** to this file for any addition, removal, or update. -- **If your project's governance requires a vote**, document or link to the vote outcome in the PR description or comments. +- **If your project's governance requires a vote**, document or link to the vote + outcome in the PR description or comments. - This process creates a public audit trail of project leadership over time. -Please email **help@finos.org** whenever this file is updated with a change to maintainership. +Please email **help@finos.org** whenever this file is updated with a change to +maintainership. diff --git a/README.md b/README.md index d8ffcffa..99ca5eec 100644 --- a/README.md +++ b/README.md @@ -34,14 +34,14 @@ ownership issues that can stall innovation. ## InnerSource SIG Leadership -| Name | Firm | Role | -| :------------- | :------------------ | :----------------------- | -| Brittany Istenes | Fannie Mae | SIG Co-Lead | -| Chamindra de Silva | Citi | SIG Co-Lead | -| Rob Moffat | FINOS | SIG Secretary | -| Peter Smulovics | Morgan Stanley | SIG Leadership Committee | -| Miguel Captiao | Deutsche bank | SIG Leadership Committee | -| Russ Rutledge | InnerSource Commons | SIG Leadership Committee | +| Name | Firm | Role | +| :----------------- | :------------------ | :----------------------- | +| Brittany Istenes | Fannie Mae | SIG Co-Lead | +| Chamindra de Silva | Citi | SIG Co-Lead | +| Rob Moffat | FINOS | SIG Secretary | +| Peter Smulovics | Morgan Stanley | SIG Leadership Committee | +| Miguel Captiao | Deutsche bank | SIG Leadership Committee | +| Russ Rutledge | InnerSource Commons | SIG Leadership Committee | ## Quick start @@ -52,7 +52,11 @@ ownership issues that can stall innovation. (or read the minutes from previous ones) ## InnerSource License Generator Working Group -The InnerSource SIG is actively developing a tool that can be used to generate InnerSource Licenses. This work is in progress in FINOS Labs and you are welcome to join the development effort [InnerSource License Generator - Github](https://github.com/finos-labs/innersource-license-generator) + +The InnerSource SIG is actively developing a tool that can be used to generate +InnerSource Licenses. This work is in progress in FINOS Labs and you are welcome +to join the development effort +[InnerSource License Generator - Github](https://github.com/finos-labs/innersource-license-generator) ## Mailing List diff --git a/docs/finos_innersource_sig_charter.md b/docs/finos_innersource_sig_charter.md index 7c4bb553..de8e2ec5 100644 --- a/docs/finos_innersource_sig_charter.md +++ b/docs/finos_innersource_sig_charter.md @@ -2,39 +2,67 @@ ### Objective -- The FINOS InnerSource SIG is a designated space to foster a culture of collaboration, openness, and shared responsibility within the FINTECH industry, leveraging InnerSource principles to improve software development processes, innovation, and operational efficiency across the organization.
 +- The FINOS InnerSource SIG is a designated space to foster a culture of + collaboration, openness, and shared responsibility within the FINTECH + industry, leveraging InnerSource principles to improve software development + processes, innovation, and operational efficiency across the organization. ### Goals -- Promote the sharing InnerSource methondologies and collaboration across different enterprises within the FINTECH sector -- Enhance the quality, security, and speed of software development by adopting best practices from the open source community -- Create a platform for continuous learning, mentorship, and knowledge exchange on cutting-edge technologies and methodologies -- Contribute to the development of open standards and reusable software components that can benefit the wider FINTECH ecosystem +- Promote the sharing InnerSource methondologies and collaboration across + different enterprises within the FINTECH sector +- Enhance the quality, security, and speed of software development by adopting + best practices from the open source community +- Create a platform for continuous learning, mentorship, and knowledge exchange + on cutting-edge technologies and methodologies +- Contribute to the development of open standards and reusable software + components that can benefit the wider FINTECH ecosystem ### Membership -- Target Members: Software developers, project managers, product owners, and anyone involved in the software development lifecycle within the FINTECH industry interested in adopting InnerSource practices +- Target Members: Software developers, project managers, product owners, and + anyone involved in the software development lifecycle within the FINTECH + industry interested in adopting InnerSource practices Membership Requirements: -- Open to all everyone of participating FINTECH organizations who are interested in or currently practicing InnerSource -- Members are expected to actively contribute to discussions, share their knowledge, and participate in SIG activities +- Open to all everyone of participating FINTECH organizations who are interested + in or currently practicing InnerSource +- Members are expected to actively contribute to discussions, share their + knowledge, and participate in SIG activities ### Activities -- Regular meetings to discuss InnerSource strategies, challenges, and best practices -- Workshops and training sessions on InnerSource principles, tools, and technologies -- Development and maintenance of a shared repository of the FINOS InnerSource SIG body of knowledge, documentation, and resources -- Facilitation of cross-team collaboration on internal projects adopting InnerSource methodologies +- Regular meetings to discuss InnerSource strategies, challenges, and best + practices +- Workshops and training sessions on InnerSource principles, tools, and + technologies +- Development and maintenance of a shared repository of the FINOS InnerSource + SIG body of knowledge, documentation, and resources +- Facilitation of cross-team collaboration on internal projects adopting + InnerSource methodologies ### When and Where - Meeting Logistics -- Monthly meetings, with ad hoc working groups meeting more frequently as needed for specific projects or initiatives -- Visit the [FINOS InnerSource SIG](https://osr.finos.org/docs/InnerSource/Introduction) to learn more on meeting cadence -- Meeting Formats are mix of in-person and virtual meetings to accommodate members from different locations - largely virtual unless we are all at a conference together -- Utilize collaboration tools like Slack, GitHub, and Zoom for ongoing communication and project collaboration -- Communication Channels: Dedicated [Slack channel](https://github.com/finos/innersource) for regular updates, discussions, and resource sharing -- Email newsletters and a dedicated section on the [FINOS OSR Core Site](https://osr.finos.org/docs/bok/Introduction) +- Monthly meetings, with ad hoc working groups meeting more frequently as needed + for specific projects or initiatives +- Visit the + [FINOS InnerSource SIG](https://osr.finos.org/docs/InnerSource/Introduction) + to learn more on meeting cadence +- Meeting Formats are mix of in-person and virtual meetings to accommodate + members from different locations - largely virtual unless we are all at a + conference together +- Utilize collaboration tools like Slack, GitHub, and Zoom for ongoing + communication and project collaboration +- Communication Channels: Dedicated + [Slack channel](https://github.com/finos/innersource) for regular updates, + discussions, and resource sharing +- Email newsletters and a dedicated section on the + [FINOS OSR Core Site](https://osr.finos.org/docs/bok/Introduction) ### Review and Approval -This charter will be reviewed annually and updated as needed to reflect the evolving goals and activities of the InnerSource SIG. Approval from senior management within the participating organizations is required to formalize the charter and commence activities + +This charter will be reviewed annually and updated as needed to reflect the +evolving goals and activities of the InnerSource SIG. Approval from senior +management within the participating organizations is required to formalize the +charter and commence activities diff --git a/docs/get-involved.md b/docs/get-involved.md index 84d11ce0..ef9d6285 100644 --- a/docs/get-involved.md +++ b/docs/get-involved.md @@ -30,7 +30,11 @@ and meetings. ## InnerSource License Generator Working Group -The InnerSource SIG is actively developing a tool that can be used to generate InnerSource Licenses. This work is in progress in FINOS Labs and you are welcome to join the development effort [InnerSource License Generator - Github](https://github.com/finos-labs/innersource-license-generator) + +The InnerSource SIG is actively developing a tool that can be used to generate +InnerSource Licenses. This work is in progress in FINOS Labs and you are welcome +to join the development effort +[InnerSource License Generator - Github](https://github.com/finos-labs/innersource-license-generator) ## Contributing diff --git a/docs/governance/raci-matrix.md b/docs/governance/raci-matrix.md index 9aeca5aa..4fae2f1f 100644 --- a/docs/governance/raci-matrix.md +++ b/docs/governance/raci-matrix.md @@ -4,13 +4,20 @@ **September 2025** -> **Source document:** [Google Docs](https://docs.google.com/document/d/1W-3hC-umkXkX4JHB5Mo-6Jl01FeX9BJqxGoB-D4Q3aM/edit?tab=t.0) +> **Source document:** > +> [Google Docs](https://docs.google.com/document/d/1W-3hC-umkXkX4JHB5Mo-6Jl01FeX9BJqxGoB-D4Q3aM/edit?tab=t.0) -The overarching theme is that **InnerSource Commons will be "Responsible" for most execution tasks**, as the primary organizer, whereas **FINOS is "Accountable" to ensure those tasks meet the foundation's requirements** and will provide support and resources. In many areas, both will collaborate (Consulted) and keep each other Informed. +The overarching theme is that **InnerSource Commons will be "Responsible" for +most execution tasks**, as the primary organizer, whereas **FINOS is +"Accountable" to ensure those tasks meet the foundation's requirements** and +will provide support and resources. In many areas, both will collaborate +(Consulted) and keep each other Informed. -The table below summarizes the **Roles (RACI)** for key activities needed to run a successful FINOS-InnerSource SIG. +The table below summarizes the **Roles (RACI)** for key activities needed to run +a successful FINOS-InnerSource SIG. **Roles:** + - **R = Responsible** (the party doing the work) - **A = Accountable** (the party ultimately answerable/approving) - **C = Consulted** (the party consulted for input) @@ -18,48 +25,75 @@ The table below summarizes the **Roles (RACI)** for key activities needed to run ## RACI Matrix -| Task / Responsibility | InnerSource Commons (ISC) | FINOS | -|---|---|---| -| **Define SIG Charter & Objectives** | C (collaborate with industry co-chairs) | R (drafts content, proposes goals) / A (approves charter via Board) | -| **SIG Leadership (Chair/Co-chair roles)** | R (provides Chair/organizer personnel; leads the group) | A (formal appointment of Chair; oversight of leadership changes) — *SIG Leads* | -| **Meeting scheduling & logistics** (set dates, arrange virtual meeting room) | R (schedules meetings, sets frequency; coordinates timing) | C (assists with Zoom/venue setup as needed; ensures platform is FINOS-approved) — *SIG Leads* | -| **Agenda preparation & circulation** | R (drafts agendas for each meeting; circulates to ISC channels and sends to FINOS list) | C (reviews agenda if needed for compliance; helps distribute via FINOS mailing list/Slack) — *SIG Leads* | -| **Meeting facilitation** (chairing the meeting) | R (hosts the call, leads discussion, keeps time) | I (may attend as participant; observes) — *SIG Leads* | -| **Antitrust & CoC compliance during meetings** | R (reminds attendees of Antitrust Policy; displays required slides; enforces code of conduct in meeting) | A (accountable that meetings adhere to Linux Foundation antitrust rules and FINOS CoC; provides standard slides/policy text) — *SIG Leads* | -| **Minute taking & attendance recording** | R (records minutes and list of attendees for each meeting) | I (does not take minutes, but receives/archives them; monitors that attendance is logged for record) — *SIG Leads* | -| **Publishing minutes to public repository** | R (writes and posts meeting minutes to FINOS GitHub or wiki; shares link with both communities) | A (ensures minutes are publicly available; repository is under FINOS org) — *SIG Leads* | -| **Promoting upcoming meetings to FINOS members** | C (provides meeting info and promotional content) / I (stays aware of FINOS comms) | R (announces meetings on FINOS Slack, mailing lists, website; invites FINOS community) — *FINOS Staff* | -| **Promoting upcoming meetings to ISC community** | R (announces meetings on ISC Slack and mailing list; invites ISC members) | I (does not execute, but is aware and can amplify if needed) | -| **Maintaining communication channels** (Slack, mailing lists) | R (manages ISC Slack channel and mailing list for InnerSource topics; moderates per ISC policies) | R (manages FINOS Slack channel and mailing list for the SIG; moderates per FINOS CoC) — *FINOS Staff* | -| **Creating SIG deliverables** (e.g. best practice docs, case studies) | R (leads content creation, drafts documents with SIG volunteers) | C (consulted on content for alignment and legal approval; reviews drafts) — *SIG Leads* | -| **Publishing deliverables on FINOS platforms** | C (contributes content and agrees on final version) | A/R (FINOS to approve and officially publish the deliverable on its site or repo under CC-BY-4.0) — *FINOS Staff* | -| **Marketing published materials to FINOS audience** | I/C (provides input on key messages) | R (distributes through FINOS blog, newsletter, social media, etc.) — *FINOS Staff* | -| **Marketing published materials to ISC audience** | R (shares through ISC blog, website, community newsletters) | I (no action needed, though FINOS may cross-post or mention in FINOS context) | -| **Presentations at FINOS events** (e.g. OSSF) | R (prepares talk proposals and presentation content; delivers talks) | C/A (helps secure speaking slots; final approval of participation as event organizer) — *SIG Leads* | -| **Presentations at ISC or other industry events** | R (secures invitations in InnerSource Commons events or other conferences; prepares and presents) | I (generally just informed, unless co-presenting) | -| **Overall SIG oversight & success tracking** | R (monitors engagement, gathers feedback from participants; proposes improvements) | A (monitors SIG's alignment with FINOS mission; may require reports on SIG progress) — *SIG Leads* | +| Task / Responsibility | InnerSource Commons (ISC) | FINOS | +| ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| **Define SIG Charter & Objectives** | C (collaborate with industry co-chairs) | R (drafts content, proposes goals) / A (approves charter via Board) | +| **SIG Leadership (Chair/Co-chair roles)** | R (provides Chair/organizer personnel; leads the group) | A (formal appointment of Chair; oversight of leadership changes) — _SIG Leads_ | +| **Meeting scheduling & logistics** (set dates, arrange virtual meeting room) | R (schedules meetings, sets frequency; coordinates timing) | C (assists with Zoom/venue setup as needed; ensures platform is FINOS-approved) — _SIG Leads_ | +| **Agenda preparation & circulation** | R (drafts agendas for each meeting; circulates to ISC channels and sends to FINOS list) | C (reviews agenda if needed for compliance; helps distribute via FINOS mailing list/Slack) — _SIG Leads_ | +| **Meeting facilitation** (chairing the meeting) | R (hosts the call, leads discussion, keeps time) | I (may attend as participant; observes) — _SIG Leads_ | +| **Antitrust & CoC compliance during meetings** | R (reminds attendees of Antitrust Policy; displays required slides; enforces code of conduct in meeting) | A (accountable that meetings adhere to Linux Foundation antitrust rules and FINOS CoC; provides standard slides/policy text) — _SIG Leads_ | +| **Minute taking & attendance recording** | R (records minutes and list of attendees for each meeting) | I (does not take minutes, but receives/archives them; monitors that attendance is logged for record) — _SIG Leads_ | +| **Publishing minutes to public repository** | R (writes and posts meeting minutes to FINOS GitHub or wiki; shares link with both communities) | A (ensures minutes are publicly available; repository is under FINOS org) — _SIG Leads_ | +| **Promoting upcoming meetings to FINOS members** | C (provides meeting info and promotional content) / I (stays aware of FINOS comms) | R (announces meetings on FINOS Slack, mailing lists, website; invites FINOS community) — _FINOS Staff_ | +| **Promoting upcoming meetings to ISC community** | R (announces meetings on ISC Slack and mailing list; invites ISC members) | I (does not execute, but is aware and can amplify if needed) | +| **Maintaining communication channels** (Slack, mailing lists) | R (manages ISC Slack channel and mailing list for InnerSource topics; moderates per ISC policies) | R (manages FINOS Slack channel and mailing list for the SIG; moderates per FINOS CoC) — _FINOS Staff_ | +| **Creating SIG deliverables** (e.g. best practice docs, case studies) | R (leads content creation, drafts documents with SIG volunteers) | C (consulted on content for alignment and legal approval; reviews drafts) — _SIG Leads_ | +| **Publishing deliverables on FINOS platforms** | C (contributes content and agrees on final version) | A/R (FINOS to approve and officially publish the deliverable on its site or repo under CC-BY-4.0) — _FINOS Staff_ | +| **Marketing published materials to FINOS audience** | I/C (provides input on key messages) | R (distributes through FINOS blog, newsletter, social media, etc.) — _FINOS Staff_ | +| **Marketing published materials to ISC audience** | R (shares through ISC blog, website, community newsletters) | I (no action needed, though FINOS may cross-post or mention in FINOS context) | +| **Presentations at FINOS events** (e.g. OSSF) | R (prepares talk proposals and presentation content; delivers talks) | C/A (helps secure speaking slots; final approval of participation as event organizer) — _SIG Leads_ | +| **Presentations at ISC or other industry events** | R (secures invitations in InnerSource Commons events or other conferences; prepares and presents) | I (generally just informed, unless co-presenting) | +| **Overall SIG oversight & success tracking** | R (monitors engagement, gathers feedback from participants; proposes improvements) | A (monitors SIG's alignment with FINOS mission; may require reports on SIG progress) — _SIG Leads_ | --- -This matrix shows that **InnerSource Commons takes on most of the hands-on responsibilities (Rs)** in organizing and driving the SIG, while **FINOS often serves as the accountable body (A)** ensuring everything is done according to policy and providing necessary approvals or infrastructure. Both ISC and FINOS will consult each other and stay informed at each step to make this collaboration seamless. +This matrix shows that **InnerSource Commons takes on most of the hands-on +responsibilities (Rs)** in organizing and driving the SIG, while **FINOS often +serves as the accountable body (A)** ensuring everything is done according to +policy and providing necessary approvals or infrastructure. Both ISC and FINOS +will consult each other and stay informed at each step to make this +collaboration seamless. --- ## Open Questions and Areas for Clarification -- **Official Communication Channel:** What will be the primary collaboration channel for the SIG's day-to-day discussions? Will FINOS's mailing list and Slack be the main forum (with ISC members encouraged to join there), or will we attempt to monitor and use both organizations' channels equally? For example, can FINOS member representatives join the InnerSource Commons Slack workspace for SIG talk, or should all substantive SIG discussion happen on FINOS infrastructure for compliance reasons? - - > *[JG] FINOS has a mailing list, and while we do have Slack, many FIS organizations are prohibited from joining it, so it's not the most effective comms channel. I'd assume the same would hold true for ISC Slack.* - -- **Role of FINOS Staff in Meetings:** Will a FINOS team member (community manager or facilitator) attend each meeting to help with notes or monitor compliance, or is ISC fully handling meetings with FINOS just in the background? In other words, do we expect any **FINOS Community team support** during calls (e.g. to start the Zoom, record sessions, or enforce the CoC), or will that duty fall entirely to the ISC organizers? - - > *[JG] FINOS can start off the series as part of training the meeting hosts how to run the calls according to policy, but FINOS staff cannot do this on continuous basis, we expect the call leads to be trained and also to take care of agendas and meeting notes.* - -- **SIG Leadership Appointments:** Since the InnerSource Commons Foundation is co-organizing, should an ISC representative be formally listed as a **co-chair or secretary of the SIG** within FINOS? Confirm who the official SIG Chair or co-chairs are going forward and if any additional process is needed (FINOS Board approval) to formalize changes. - - > *[JG] No Board approval needed to appoint another co-chair.* - -- **Handling of Action Items:** How will the SIG track ongoing action items or work streams (outside of meeting minutes)? Will we use the GitHub issues in the FINOS InnerSource repo to log tasks or decisions? +- **Official Communication Channel:** What will be the primary collaboration + channel for the SIG's day-to-day discussions? Will FINOS's mailing list and + Slack be the main forum (with ISC members encouraged to join there), or will + we attempt to monitor and use both organizations' channels equally? For + example, can FINOS member representatives join the InnerSource Commons Slack + workspace for SIG talk, or should all substantive SIG discussion happen on + FINOS infrastructure for compliance reasons? + + > _[JG] FINOS has a mailing list, and while we do have Slack, many FIS + > organizations are prohibited from joining it, so it's not the most effective + > comms channel. I'd assume the same would hold true for ISC Slack._ + +- **Role of FINOS Staff in Meetings:** Will a FINOS team member (community + manager or facilitator) attend each meeting to help with notes or monitor + compliance, or is ISC fully handling meetings with FINOS just in the + background? In other words, do we expect any **FINOS Community team support** + during calls (e.g. to start the Zoom, record sessions, or enforce the CoC), or + will that duty fall entirely to the ISC organizers? + + > _[JG] FINOS can start off the series as part of training the meeting hosts + > how to run the calls according to policy, but FINOS staff cannot do this on + > continuous basis, we expect the call leads to be trained and also to take + > care of agendas and meeting notes._ + +- **SIG Leadership Appointments:** Since the InnerSource Commons Foundation is + co-organizing, should an ISC representative be formally listed as a **co-chair + or secretary of the SIG** within FINOS? Confirm who the official SIG Chair or + co-chairs are going forward and if any additional process is needed (FINOS + Board approval) to formalize changes. + + > _[JG] No Board approval needed to appoint another co-chair._ + +- **Handling of Action Items:** How will the SIG track ongoing action items or + work streams (outside of meeting minutes)? Will we use the GitHub issues in + the FINOS InnerSource repo to log tasks or decisions? - **Main Contacts:** Personal email addresses vs shared mailboxes. @@ -67,19 +101,57 @@ This matrix shows that **InnerSource Commons takes on most of the hands-on respo ## FINOS Governance Requirements for SIGs -When operating a joint Special Interest Group (SIG) under FINOS governance, certain **rules and best practices** must be followed to ensure compliance and a successful collaboration. Key FINOS requirements include: - -- **Formal Charter & Leadership:** Every FINOS SIG needs a publicly documented **charter** defining its purpose, and an appointed **SIG Chair** (with possible co-chairs). The FINOS Board approves the SIG (including its charter and initial chair), and any changes (new chairs or charter updates) should be formally recorded.[^1] This ensures clear objectives and leadership structure from the start. - -- **Compliance with Policies:** All SIG activities must **abide by FINOS and Linux Foundation policies**, notably the **Antitrust Policy** and the **Community Code of Conduct**.[^2] This means meetings and collaboration should avoid any anti-competitive behavior and maintain a welcoming, inclusive environment. In practice, organizers must present an antitrust compliance reminder (e.g. a slide) at the start of each meeting and ensure discussions stay within permitted boundaries.[^3] - -- **Meeting Procedures:** FINOS has specific guidelines for running meetings. Organizers should schedule meetings **well in advance (at least 7 days)** and use approved channels (FINOS Zoom conferencing, etc.) for calls.[^4] An **agenda must be prepared and circulated** beforehand to the group's mailing list or Slack.[^5] Meetings should be open to all interested participants and ideally held at a time accessible to most of the community. - -- **Record-Keeping (Minutes & Attendance):** For transparency and legal compliance, **minutes must be taken for each meeting**.[^6] Minutes should include a list of attendees, key discussion points, any proposals or decisions made, and action items. Notably, FINOS advises **not to attribute comments by name in minutes** without permission, to encourage open dialogue.[^7] After the meeting, organizers **must publish the minutes publicly** (for example, in the SIG's GitHub repository or FINOS wiki) so that both FINOS and InnerSource Commons communities can access them.[^8] This also helps record attendance over time. - -- **Open Outputs and IP:** Any documentation or outputs produced by the SIG (e.g. white papers, guides) should be made available under an open license. FINOS specifies that **SIG contributions are made available under CC-BY-4.0 license**.[^9] This allows both FINOS and InnerSource Commons to share and re-use content freely. (For software code contributions, FINOS would require CLAs and Apache 2.0 licensing, but since this SIG is focused on best practices, code contributions are less likely.) - -- **Collaborative Principles:** FINOS expects SIGs to follow open collaboration best practices. This includes using public communication channels, responding to community inquiries, and ensuring all interested parties (regardless of FINOS membership) can participate meaningfully.[^10][^11] In this joint context, it means balancing the use of FINOS and InnerSource Commons channels to include everyone, while ultimately **operating under FINOS's "safe harbor" environment** for any official joint work. +When operating a joint Special Interest Group (SIG) under FINOS governance, +certain **rules and best practices** must be followed to ensure compliance and a +successful collaboration. Key FINOS requirements include: + +- **Formal Charter & Leadership:** Every FINOS SIG needs a publicly documented + **charter** defining its purpose, and an appointed **SIG Chair** (with + possible co-chairs). The FINOS Board approves the SIG (including its charter + and initial chair), and any changes (new chairs or charter updates) should be + formally recorded.[^1] This ensures clear objectives and leadership structure + from the start. + +- **Compliance with Policies:** All SIG activities must **abide by FINOS and + Linux Foundation policies**, notably the **Antitrust Policy** and the + **Community Code of Conduct**.[^2] This means meetings and collaboration + should avoid any anti-competitive behavior and maintain a welcoming, inclusive + environment. In practice, organizers must present an antitrust compliance + reminder (e.g. a slide) at the start of each meeting and ensure discussions + stay within permitted boundaries.[^3] + +- **Meeting Procedures:** FINOS has specific guidelines for running meetings. + Organizers should schedule meetings **well in advance (at least 7 days)** and + use approved channels (FINOS Zoom conferencing, etc.) for calls.[^4] An + **agenda must be prepared and circulated** beforehand to the group's mailing + list or Slack.[^5] Meetings should be open to all interested participants and + ideally held at a time accessible to most of the community. + +- **Record-Keeping (Minutes & Attendance):** For transparency and legal + compliance, **minutes must be taken for each meeting**.[^6] Minutes should + include a list of attendees, key discussion points, any proposals or decisions + made, and action items. Notably, FINOS advises **not to attribute comments by + name in minutes** without permission, to encourage open dialogue.[^7] After + the meeting, organizers **must publish the minutes publicly** (for example, in + the SIG's GitHub repository or FINOS wiki) so that both FINOS and InnerSource + Commons communities can access them.[^8] This also helps record attendance + over time. + +- **Open Outputs and IP:** Any documentation or outputs produced by the SIG + (e.g. white papers, guides) should be made available under an open license. + FINOS specifies that **SIG contributions are made available under CC-BY-4.0 + license**.[^9] This allows both FINOS and InnerSource Commons to share and + re-use content freely. (For software code contributions, FINOS would require + CLAs and Apache 2.0 licensing, but since this SIG is focused on best + practices, code contributions are less likely.) + +- **Collaborative Principles:** FINOS expects SIGs to follow open collaboration + best practices. This includes using public communication channels, responding + to community inquiries, and ensuring all interested parties (regardless of + FINOS membership) can participate meaningfully.[^10][^11] In this joint + context, it means balancing the use of FINOS and InnerSource Commons channels + to include everyone, while ultimately **operating under FINOS's "safe harbor" + environment** for any official joint work. --- diff --git a/docs/isc_finos_partnership.md b/docs/isc_finos_partnership.md index 801a4c33..765782c0 100644 --- a/docs/isc_finos_partnership.md +++ b/docs/isc_finos_partnership.md @@ -1,41 +1,99 @@ ## Why are InnerSource Commons and FINOS collaborating? -InnerSource Commons and FINOS recognize the synergies between InnerSource practices and the goals of fostering open collaboration and innovation in the financial services industry. By working together, they aim to create a powerful ecosystem that promotes the adoption of InnerSource methodologies and accelerates the development and adoption of open-source solutions in the financial sector. +InnerSource Commons and FINOS recognize the synergies between InnerSource +practices and the goals of fostering open collaboration and innovation in the +financial services industry. By working together, they aim to create a powerful +ecosystem that promotes the adoption of InnerSource methodologies and +accelerates the development and adoption of open-source solutions in the +financial sector. ### FAQ -**What benefits does the collaboration between [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/) offer to organizations?** +**What benefits does the collaboration between +[InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/) offer to organizations?** -- This collaboration provides organizations with a unique opportunity to leverage the expertise of two influential communities. It facilitates the exchange of best practices in InnerSource, enabling financial institutions to drive innovation, enhance collaboration, and benefit from the collective knowledge of both InnerSource Commons and FINOS. +- This collaboration provides organizations with a unique opportunity to + leverage the expertise of two influential communities. It facilitates the + exchange of best practices in InnerSource, enabling financial institutions to + drive innovation, enhance collaboration, and benefit from the collective + knowledge of both InnerSource Commons and FINOS. **How will this collaboration impact the financial services industry?** -- The collaboration between [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/) is poised to bring about transformative changes in the financial services industry. By combining forces, the organizations aim to accelerate the development of open-source projects tailored to the unique needs of the financial sector, fostering a culture of collaboration, transparency, and innovation. - -**Can organizations participate in both [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/) initiatives simultaneously?** - -- Yes, organizations are encouraged to actively engage with both InnerSource Commons and FINOS initiatives. The collaboration is designed to provide a seamless experience for organizations looking to adopt InnerSource practices while contributing to and benefiting from the open-source projects hosted by FINOS. - -**What collaborative initiatives can organizations expect from [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/)?** - -- The collaboration will manifest in joint events, webinars, and working groups that bring together professionals from the InnerSource and financial technology communities. These initiatives will serve as platforms for knowledge sharing, networking, and collaborative problem-solving, providing valuable insights to organizations navigating the intersection of InnerSource and financial services. - -**How can organizations get involved in the collaborative efforts between [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/)?** - -- Organizations can actively participate by joining relevant working groups within both foundations, attending SIG level meetings, and contributing to joint projects/initiatives. Both InnerSource Commons and FINOS provide channels for organizations to connect, share experiences, and collaborate on initiatives that align with their goals. - -**Will there be specific projects addressing the needs of the financial services industry?** - -- Yes, the collaboration will focus on identifying and addressing the specific challenges and opportunities within the financial services sector. Joint projects will be initiated to develop open-source solutions that cater to the unique requirements of financial institutions, fostering innovation and efficiency. - -**How can organizations stay informed about the progress of the collaboration between [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/)?** - -- Regular updates, announcements, and insights about the collaboration will be shared through official communication channels, including newsletters, websites, and social media. Organizations are encouraged to stay engaged and subscribe to these channels to remain informed about the latest developments and opportunities for involvement. - -**Are there any costs associated with participating in the collaborative initiatives between [InnerSource Commons](https://innersourcecommons.org/) and [FINOS](https://www.finos.org/)?** - -- Both InnerSource Commons and FINOS are committed to fostering open collaboration and do not impose membership fees for participation. However, organizations may incur costs related to specific events, training programs, or project contributions. - -**How can organizations provide feedback or seek additional information about the collaboration?** - -- Organizations are encouraged to reach out to the respective contacts at InnerSource Commons and FINOS for any inquiries, feedback, or additional information about the collaborative initiatives. Open communication is valued, and both organizations are dedicated to supporting organizations in their journey towards successful InnerSource adoption in the financial services industry. +- The collaboration between + [InnerSource Commons](https://innersourcecommons.org/) and + [FINOS](https://www.finos.org/) is poised to bring about transformative + changes in the financial services industry. By combining forces, the + organizations aim to accelerate the development of open-source projects + tailored to the unique needs of the financial sector, fostering a culture of + collaboration, transparency, and innovation. + +**Can organizations participate in both +[InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/) initiatives simultaneously?** + +- Yes, organizations are encouraged to actively engage with both InnerSource + Commons and FINOS initiatives. The collaboration is designed to provide a + seamless experience for organizations looking to adopt InnerSource practices + while contributing to and benefiting from the open-source projects hosted by + FINOS. + +**What collaborative initiatives can organizations expect from +[InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/)?** + +- The collaboration will manifest in joint events, webinars, and working groups + that bring together professionals from the InnerSource and financial + technology communities. These initiatives will serve as platforms for + knowledge sharing, networking, and collaborative problem-solving, providing + valuable insights to organizations navigating the intersection of InnerSource + and financial services. + +**How can organizations get involved in the collaborative efforts between +[InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/)?** + +- Organizations can actively participate by joining relevant working groups + within both foundations, attending SIG level meetings, and contributing to + joint projects/initiatives. Both InnerSource Commons and FINOS provide + channels for organizations to connect, share experiences, and collaborate on + initiatives that align with their goals. + +**Will there be specific projects addressing the needs of the financial services +industry?** + +- Yes, the collaboration will focus on identifying and addressing the specific + challenges and opportunities within the financial services sector. Joint + projects will be initiated to develop open-source solutions that cater to the + unique requirements of financial institutions, fostering innovation and + efficiency. + +**How can organizations stay informed about the progress of the collaboration +between [InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/)?** + +- Regular updates, announcements, and insights about the collaboration will be + shared through official communication channels, including newsletters, + websites, and social media. Organizations are encouraged to stay engaged and + subscribe to these channels to remain informed about the latest developments + and opportunities for involvement. + +**Are there any costs associated with participating in the collaborative +initiatives between [InnerSource Commons](https://innersourcecommons.org/) and +[FINOS](https://www.finos.org/)?** + +- Both InnerSource Commons and FINOS are committed to fostering open + collaboration and do not impose membership fees for participation. However, + organizations may incur costs related to specific events, training programs, + or project contributions. + +**How can organizations provide feedback or seek additional information about +the collaboration?** + +- Organizations are encouraged to reach out to the respective contacts at + InnerSource Commons and FINOS for any inquiries, feedback, or additional + information about the collaborative initiatives. Open communication is valued, + and both organizations are dedicated to supporting organizations in their + journey towards successful InnerSource adoption in the financial services + industry. diff --git a/docs/team.md b/docs/team.md index 00206b70..05ee6ce9 100644 --- a/docs/team.md +++ b/docs/team.md @@ -3,11 +3,11 @@ id: team title: SIG Leadership Team --- -| Name | Firm | Role | -| :------------- | :------------------ | :----------------------- | -| Brittany Istenes | Fannie Mae | SIG Co-Lead | -| Chamindra de Silva | Citi | SIG Co-Lead | -| Rob Moffat | FINOS | SIG Secretary | -| Peter Smulovics | Morgan Stanley | SIG Leadership Committee | -| Miguel Captiao | Deutsche bank | SIG Leadership Committee | -| Russ Rutledge | InnerSource Commons | SIG Leadership Committee | +| Name | Firm | Role | +| :----------------- | :------------------ | :----------------------- | +| Brittany Istenes | Fannie Mae | SIG Co-Lead | +| Chamindra de Silva | Citi | SIG Co-Lead | +| Rob Moffat | FINOS | SIG Secretary | +| Peter Smulovics | Morgan Stanley | SIG Leadership Committee | +| Miguel Captiao | Deutsche bank | SIG Leadership Committee | +| Russ Rutledge | InnerSource Commons | SIG Leadership Committee |