# (03/19/2026) Meeting Minutes ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | Term | | ------------------------ | ---------- | ---------- | ----------------- | ------------ | | Georg Link | Yes | Chair | Y | April 2026 | | Udai Solanki | Yes | Vice Chair | Y | October 2026 | | Terence ‘Tex’ McCutcheon | Yes | Secretary | N | N/A | | Bernard Sibanda | Yes | Member | Y | October 2026 | | Jordan Hill | Yes | Member | Y | October 2026 | | Sebastian Pabon | Yes | Member | Y | October 2026 | | Reshma Mohan | Yes | Member | Y | October 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | | Empty Seat | No | Member | Y | April 2026 | Community/Other Attendees * Dan Baruka * Harun Mwangi * Jean-Philippe Raynaud * Luke Mahoney (MLabs) * Mike Hornan * Uche Obasi **Recording:** [Open Source Committee (Intersect) - 2026/03/19 - Recording](https://drive.google.com/file/d/1zsyvNKd-vdAfvs7yrTcSCWY68Yv3dsa4/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/03/19 - Transcript](https://docs.google.com/document/d/1CyosF0hUjJtMdUTf3hhjMsY2-Vtn4izDTSTpFlmRKZA/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/03/19 – Chat Transcript](https://drive.google.com/file/d/1lxUHWHwke2rLcjWtb5FmZaVae9fNIMN0/view?usp=sharing) ## Intros **Tex:** Open Source Program Manager, Intersect Staff, Open Source Committee Secretary\\\ **Bernard:** TBD\ **Georg:** Bitergia\ **Jordan:** TBD\ **Reshma:** OSC voting member, Founder of Reafino\ **Sebastian:** OSC, Gimbalabs, contributor, Andamio co-founder.\ **Udai:** OSC voting member, Founder and CEO - AIQUANT ## Agenda 03.19.26 * Developer Advocate Check-In * Mithril Signer addition to Cardano Node * OSS Planning Updates * TSP Confirm Decisions * MRP Confirm Decisions * Open Forum ## Decisions/Actions **Decisions** * **Mithril Integration Deferral:** The committee decided to postpone a decision on including the Mithril Signer binary in the Cardano node for two weeks to allow for technical review. * **Open Source Summit Sponsorship:** Confirmed the Cardano Foundation as a co-sponsor; the contract with the Linux Foundation is approved to move toward signing by next week. * **Summit Branding:** Agreed to brand the event booth as "Cardano" with Intersect and CF logos as subsets to drive broader ecosystem adoption. * **Tooling Budget Allocation:** Confirmed that approximately 800,000+ ADA remains available for the Tooling Sustainability Program, with some potentially redirected to support the "Dora" hard fork. * **Maintainer Review Threshold:** Reaffirmed the rule that feedback from two committee members is sufficient to move a maintainer applicant forward. **Actions** * **Documentation Distribution:** Jean-Philippe to provide the committee with the written proposal and technical documentation regarding the Mithril Signer integration. * **Technical Deep Dive:** Udai and Georg to review the Mithril binary proposal specifically regarding "open source philosophy" and security transparency. * **Adoption Metrics Request:** Terence to formulate and send specific questions to Luke and Ben (MLabs) regarding "organic" adoption (users not contracted by MLabs) for CTL, YTXP, and other tools. * **Budget Reconciliation:** Terence to finalize the Builderfest payout to determine the exact remaining balance for potential attendance at Paris Blockchain Week. * **Application Process Update:** Sebastian to move the Tooling Sustainability planning document to the shared drive; Committee to review and update application questions to reduce "blockers" for applicants. * **Milestone Review:** Udai to go through the 36+ submitted milestones for the Developer Advocates on Project Board 71. * **Conference Reporting:** Jordan to publish and upload the formal report from last week's conference to the shared drive. | Topic | Discussion | Notes | | --------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Funding Process Overview | Luke (MLabs) inquired about the evolution of the Treasury withdrawal process from 2025 to 2026. | Terence clarified that 2025 focused on "buckets" aligned with strategy pillars; 2026 processes are still being finalized. | | Developer Advocate Update | Uche provided an update on Q1 milestones, including DevX sessions and spotlight calls. | Focused on meeting end-of-quarter milestones for OSC review. | | Milestone Review Status | Udai and Terence discussed the volume of pending milestones (approx. 36–55 items across four advocates). | Milestones are tracked via Project Board 71; "Review" column is the priority for OSC action. | | Q2 Developer Feedback | Terence outlined the Q2 goal: each advocate must log 10 pieces of developer feedback and take action. | Data is being collected in the DevX repository and will be published to Gitbook. | | Mithril Signer Integration | Proposal to include the Mithril Signer binary in the Cardano node (starting v10.8) to increase SPO adoption. | Controversial: Georg expressed strong concerns about including binaries in open source due to transparency issues. | | Mithril Technical Context | Jean-Philippe (JP) explained that Mithril provides fast bootstrapping and state proofs but needs SPO engagement. | JP noted that DMQ node is already included; adding the signer is the "logical next step" for security. | | Mithril Decision Deferral | Committee requested more documentation and time to review the technical impact. | Action: Revisit in two weeks. JP to provide documentation to the committee. | | Conference Report | Jordan shared highlights from a recent blockchain conference regarding paid open source models. | A full written report is forthcoming; positive engagement with SUI and GDAU groups. | | Open Source Summit Planning | Update on the event (May 18–20). Cardano Foundation (CF) is co-sponsoring. | Contract with Linux Foundation to be signed by next week. Booth branded as "Cardano." | | Summit Budget & Travel | Terence reviewed travel costs for 12 attendees (Speakers, CF, and Dev Advocates). | Current estimates (\~$19.5k) are under the original $87k budget due to secured group rates. | | Tooling Sustainability | Discussion on funding existing tools (CTL, YTXP, TX Village) using remaining 800k+ ADA budget. | Udai emphasized that "utilization" must be the primary criteria for sustainability funding. | | Tooling Adoption Metrics | Luke (MLabs) provided a "gist" of adoption for CTL and others but lacked hard data. | Action: Luke to source specific "organic" adoption metrics (non-MLabs users) for the next meeting. | | Application Process Review | Committee discussed the need to improve how information is gathered upfront in applications. | Terence to formulate specific questions for MLabs and check the shared drive for the planning doc. | | Maintainer Retainer Program | Final call for feedback on interviewed maintainer candidates. | Sebastian noted a preference for maintainers to be sent by the projects themselves to avoid "blockers." | | Program Participation | Bernard and Udai discussed why applicant numbers are low despite advertising. | Potential blockers: high qualification requirements and conflicts with full-time employment schedules. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/03-19-2026-meeting-minutes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.