finos · rrrutledge · Jul 30, 2026
diff --git 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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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