> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/06-25-2026-meeting-minutes.md). # (06/25/2026) Meeting Minutes ## Attendees:
NameAttendanceRoleVoting Seat (Y/N)Term Ends
Sebastian PabonYesChairYApril 2027
Kambale Mechack ElieYesVice ChairYApril 2028
Terence β€˜Tex’ McCutcheonYesSecretaryNN/A
Bernard SibandaYesMemberYApril 2027
Jordan HillYesMemberYApril 2027
Udai SolankiYesMemberYApril 2027
Reshma MohanYesMemberYApril 2027
Pawel JakubasYesMemberYApril 2028
Olivier MwatsimulamoYesMemberYApril 2028
Bora ObenYesMemberYApril 2028
Dominik HinklemanNoMemberYApril 2028
Community/Other Attendees * Benjamin Hart * Dan Baruka * Emmanuel Titi * Harun Mwangi * Luke Mahoney * Uche Obasi **Recording:** [Open Source Committee (Intersect) - 2026/06/25 - Recording](https://drive.google.com/file/d/1B5QAN6rfOxU2LtiPGk-IVIwn6lmER8tI/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/06/25 - Transcript](https://docs.google.com/document/d/1MB8a_3FieY-QIy7SXxMpFFHhPMqfVWgJyC5NKbVUfOU/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/06/25 – Chat Transcript](https://drive.google.com/file/d/1GQDOiU5kIeYHF7VlP5V1PSOO0uqvolB-/view?usp=sharing) ## Intros **Bora:** TBD\ **Bernard:** OSC - voting member\ **Dominik:** OSC comittee member. Part of the company Inferara\ **Jordan:** TBD\ **Kambale:** Open Source Committee. Software Developer\ **Olivier:** Goma Hub Member, Milestone Reviewer-Project Catalyst, MCC and OSC\ **Pawel:** OSC member, Cardano Foundation\ **Reshma:** OSC voting member\ **Sebastian:** OSC, Gimbalabs, contributor, Andamio co-founder.\ **Tex:** Open Source Program Manager, Intersect Staff, Open Source Committee Secretary\ **Udai:** Member, OSC, AIQUANT Technologies ## Agenda 6.25.26 * Developer Advocate Check In * Actions from the Last Meeting * Intersect Planning Q2/Q3 * Budget Discussion (Tweaks?) * MRP Update * Approve Plutonomicon/CTL SoW * Open Forum ## Decisions/Actions **Decisions** * **Approval of CTL Statement of Work (SOW):** The committee officially approved the statement of work for the CTL tooling initiative, with at least seven members in agreement. * **Maintainer Retainer Program Cohort Finalized:** The committee finalized the selection of 20 candidates (6 enrolled, 14 new), confirming all contracts were signed. * **Q3 Strategic Goal Definition:** The committee agreed that the primary objective for Q3 2026 will be closing out the 2025 Treasury Spend (Paid Open Source Model V1). **Actions** * **Review Q2 Submissions:** All committee members must visit the GitHub Project Board (Project 71) in the Open Source Office repository to review and leave feedback on the work submitted by the Developer Advocates. (Time-sensitive: approx. 5 days remaining). * **Contribute to Intersect Planning Draft:** Committee members need to access the shared Google Doc link (to be provided in Discord by Terence) to review, highlight Q2 milestones, and add missing Q3 initiatives ahead of Monday's alignment meeting. * **Share Availability for Deep Dives:** Committee members must share their scheduling availability in the Discord channel so Terence can set up off-cycle working sessions for the budget and the maintainer retainer program. * **Process Approved SOW:** Terence to process the approved CTL statement of work on the back end to get funding rolling. | Topic | Discussion | Notes | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Developer Advocate Program Transitions | Terence provided an operational update indicating that developer advocates are in their final month of contracted engagement (ending June). There is an ongoing ask for them to retain their titles and contribute voluntarily, though no contractual requirement exists after June. They are expected to continue running the working group meetings. |

Action Required: Committee members need to review Q2 work on GitHub Project Board 71 and leave feedback.

Timeline: Roughly 5 calendar days remaining for advocates to submit final inputs.

| | Developer Advocate Report | Dan (Developer Advocate) confirmed that they are at the end of their contract and Q2 cycle. They are currently submitting their final report via the GitHub project board and affirmed they will continue to maintain and participate in developer experience sessions. | Dan verified that Terence's summary aligned precisely with the team's transition status. | | Maintainer Retainer Program Status | Terence confirmed that all selected candidates signed their contracts, finishing just one day past the provisional deadline. A total of 20 people are selected for the program: 6 previously enrolled and 14 new individuals to be onboarded in the coming week. |

The program spans a 12-month window.

Future Strategy: Future iterations may explore shorter 6-month terms instead of 12 months, pending committee evaluation.

| | Developer Experience (DevX) Survey Feedback | Terence noted an outstanding action item to gather feedback on the DevX survey. The document was likely shared within the developer advocate channels accessible by the committee. | Terence will publish this on GitBook as signed off by the advocates, indicating that official approval/tweaks from the committee are still pending. | | Intersect Planning Document Contributions | Terence requested more proactive back-and-forth contributions to the Intersect planning draft. Bernard added and expanded thoughts based on instruction templates, but more committee wide peer-review is requested. | Action Item: Terence to drop the Google Doc link into the Discord channel. Committee members are asked to highlight achieved Q2 items or add missing Q3 initiatives. | | Tooling Proposals & Invoices | Under the tooling program, funds are still available to be awarded. Terence noted outreach regarding critical tooling hardships (e.g., TAP tools). Additionally, a reminder was issued to submit outstanding travel invoices; only one committee member remains outstanding. | Committee members with personal connections to vulnerable projects are urged to encourage them to submit proposals. | | Q2/Q3 Strategy Planning Board | Terence shared the committee collaboration board link via Discord to establish clear Q3 milestones. A critical target identified for Q3 is closing out the 2025 Treasury Spend (Paid Open Source Model V1). | Sebastian highlighted that he, Bernard, and Reshma added Q2/Q3 perspectives into the working document to prep for upcoming multi-committee alignment meetings. | | Developer Experience Innovation Working Group | Terence invited more committee members to join the Developer Experience Innovation Working Group, which meets once a month. Bora (a developer portal maintainer) is actively involved. Bora requested the invitation link as he hadn't received it yet. | Terence clarified that this group stems from recent collaborative sessions with Laura. | | Budget Resubmission Strategy | Following a rejected omnibus proposal from Intersect OSC, encompassing 5 core programs, the committee held a debate on how to proceed. A DREP feedback comment suggested breaking down the Paid Open Source Model package into separate individual proposals. |

Bora's View: Governance is highly complex; separating packages (like prioritizing Maintainer Retainer and Tooling) or showing stronger ROI metrics is necessary.

Sebastian's View: Agreed with splitting the proposal and suggested better external communication of the committee's work.

| | Program Value Definitions & Messaging | The committee evaluated ecosystem trends where major projects (like TX Pipe) bypassed the Open Source Office to ask the general Treasury for multi-million ADA maintenance budgets. |

Pawel's View: Suggested narrowing the core mission to critical infrastructure or expanding scope explicitly to include security audits or premium CLI support.

Udai's View: Pointed out that tight rules restricting corporate entities from the Maintainer Retainer program might drive companies directly to the general treasury instead.

| | Clarifying Open Source Compensation | Terence firmly defended the program's foundational mandate against assertions that the compensation is too low. He reminded the committee that the program provides motivational stipends for dedicated maintainers, not full-time developer salaries. | Terence cautioned against undermining the program's philosophy publicly, emphasizing that its goal is to keep open-source projects alive, not to act as a development agency. | | Tooling Statement of Work (SOW) | The committee reviewed the proposed Statement of Work for CTL. Ben and Luke were present to field any inquiries. Bora questioned the sequencing of approving a budget prior to an approved SOW, which Terence and Ben clarified is standard practice for Intersect applications. | Vote Outcome: More than 6-7 members expressed explicit agreement. The SOW was officially approved by the committee, and Terence will process it on the back end. | | Financial Templates & Currency Slippage | Luke requested structural clarification on next steps regarding fees and the choice between 2025 vs 2026 templates. Terence clarified that Intersect does not deduct fees from the committee's allocated tooling allocations; the full 30,000 will be paid based on milestone progress. | Currency Notes: Ben advised that the administration is leaning strictly toward ADA rather than USDCX due to lack of stablecoin liquidity and an inability to manage slippage on Cardano. | | Meeting Close & Off-Cycle Planning | Terence adjourned the meeting and announced that he will arrange off-cycle deep-dive workshops specifically focused on budget allocations and the maintainer retainer program. | Action Item: Committee members are asked to share their weekly availability in Discord to schedule these deep dives. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/06-25-2026-meeting-minutes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.