> 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-11-2026-meeting-minutes.md). # (06/11/2026) Meeting Minutes ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | Term | | ------------------------ | ---------- | ---------- | ----------------- | --------------- | | Sebastian Pabon | Yes | Chair | Y | October 2025 | | Kambale Mechack Elie | Yes | Vice Chair | Y | April 2026 (2y) | | Terence ‘Tex’ McCutcheon | Yes | Secretary | N | N/A | | Bernard Sibanda | Yes | Member | Y | October 2025 | | Jordan Hill | Yes | Member | Y | October 2025 | | Udai Solanki | No | Member | Y | October 2025 | | Reshma Mohan | Yes | Member | Y | October 2025 | | Pawel Jakubas | No | Member | Y | April 2026 (2y) | | Olivier Mwatsimulamo | Yes | Member | Y | April 2026 (2y) | | Bora Oben | Yes | Member | Y | April 2026 (2y) | | Dominik Hinkleman | Yes | Member | Y | April 2026 (2y) | Community/Other Attendees * Benjamin Hart * Emmanuel Mutisya * Emmanuel Titi * Luke Mahoney * Mike Hornan * Uche Obasi **Recording:** [Open Source Committee (Intersect) - 2026/06/11 - Recording](https://drive.google.com/file/d/1Ml7G6FbKNrgYtLsSxqjKESZKAYoaNnep/view?usp=drive_link) **Transcript:** [Open Source Committee (Intersect) - 2026/06/11 - Transcript](https://docs.google.com/document/d/1PXVlxujJx_zT4fhSI65IlHKAl4gwgP2shy3LAQaN10Y/edit?usp=drive_link) **Chat Transcript:** [Open Source Committee Meeting – 2026/06/11 – Chat Transcript](https://drive.google.com/file/d/1QIKOqKvVDEdjVq-cjZriQ0woP-dwiRtB/view?usp=drive_link) ## 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:** TBD ## Agenda 6.11.26 * Developer Advocate Check In * Discuss MRP interviews and selections * Intersect Planning * General planning for Budget rewrite * Open Forum ## Decisions/Actions **Decisions** * **Official Chair Appointed:** Sebastian was officially voted in and confirmed as the Chair for the Open Source Committee. * **CTL Proposal Approval:** The Cardano Transaction Lib (CTL) proposal by MLabs was confirmed as officially approved and integrated into the program, with only the final shape of the milestones left to be determined. * **Reporting Method Pivot:** The committee decided to handle the Intersect Quarterly Planning Report asynchronously via Discord rather than dedicating 30 minutes of live meeting time, due to the high volume of newly appointed members. **Actions** * **Review and Grade Interviews:** All committee members must access the shared drive over the weekend to review candidate recordings and log their star ratings. * **Provide Feedback on DevX Survey:** Committee members need to review the Developer Experience Survey link shared by Emmanuel in Discord and leave their comments before the final report is published. * **Contribute to Intersect Planning Document:** Members must collaborate asynchronously on the shared planning document to outline Q2 achievements and Q3 priorities. * **Review Developer Advocates Submissions:** As June concludes, members must check the OSC/TSC Review column on the project board to audit completed developer advocate submissions and write-ups. * **Submit Tooling Proposals:** Members are tasked with identifying and submitting critical ecosystem tools that are suffering or in need of emergency funding (Bands 3 and 4) to help the committee hit its 5-project milestone threshold. * **Submit Outstanding Invoices:** Any committee member who has not yet submitted their invoice for the summit travel expenses must do so immediately. | Topic | Discussion | Notes / Action Items | | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Meeting Commencement & Leadership Change | Terence kicked off the meeting and congratulated Sebastian on being voted in as the official Chair for the Open Source Committee. Terence passed meeting leadership to Sebastian. | Action: Sebastian to lead current and future sessions. Committee members are encouraged to remain on camera when possible. | | 2. Review of Interview Evaluation Files | Terence introduced the grading spreadsheet for the Maintainer Retainer Program interviews. He clarified formatting: questions in green were asked, and questions in red were skipped. | Action: All committee members (excluding Terence) must review the shared drive and input their star ratings over the weekend. At least 3 scores per applicant are required to proceed. | | 3. Accessing Shared Committee Files | Dominik asked where the evaluation files and shared materials are located. Terence clarified the file path structure. | Notes: Files are located in the protected Google Drive folder: Open source committee \\/ Possum 2526 retainer program. | | 4. ClickUp vs. Google Sheets Data | Dominik questioned if data is synced between ClickUp and Google Sheets. Terence explained the distinct uses of both platforms. | Notes: Base applicant data is housed in ClickUp, while active interview analysis and grading are conducted in Google Sheets for easier tracking. | | 5. Developer Advocate Weekly Report | Emmanuel delivered the weekly report, highlighting a weekend virtual French-language session on smart contracts hosted by Dan to boost language diversity. | Notes: The team is focusing on expanding reach to non-English speaking developer demographics. | | 6. Developer Experience Survey Results | Emmanuel shared the newly finalized Developer Experience Survey link for committee review. The survey highlighted critical community pain points and proposed solutions. | Action: Committee members to review the link in Discord and provide comments before the final report is published. | | 7. Developer Portal Documentation Debate | Bora noted that some community "pain points" (like lacking offline developer environments) already exist and are fully documented on the Cardano Developer Portal. | Notes: Emmanuel and Bora noted that the issue is lack of user awareness. Emmanuel suggested updating the DevX report or Developer Portal to better highlight existing debugging tools. | | 8. Maintainer Retainer Program Progress | Sebastian noted that interviews are ongoing and thanked Rejma for his consistent attendance and guidance during the evaluation sessions. | Action: Sebastian will share calendar invitations for next week's interviews. Members are explicitly tasked with vetting if candidates possess the right baseline skills for their respective projects. | | 9. Security Framework Update | Sebastian attempted to give Mike 5 minutes to present updates regarding the security framework, but Mike experienced technical difficulties. | Notes: Mike was unable to speak due to internet connection issues. Security documents will be shared asynchronously or deferred to the next meeting. | | 10. Intersect Quarterly Planning Report | Sebastian and Terence discussed an Intersect organizational requirement to compile a Q2/Q3 quarterly report covering achievements, values, risks, and future focus areas. | Action: Sebastian shared a sync document link. Due to many members being new, this exercise will be completed asynchronously on Discord over the week. | | 11. Budget Proposal Rewrite Strategy | Sebastian and Terence introduced the need to plan for a post-scenario rewrite if the current budget proposal is rejected by the community reps. | Notes: The committee needs to review community comments and potentially restructure the proposal from a 1.5-year timeline down to a holistic 1-year timeline for 2027. | | 12. MLabs Project Status (CTL & Lambda Buffers) | Luke from MLabs requested a status update on the Cardano Transaction Lib (CTL) and Lambda Buffers proposals, offering to provide further scoping documents if needed. | Notes: Sebastian confirmed CTL is officially approved and in the program. The committee is finalizing the specific shape of the milestones and will deliver a conclusive decision to MLabs shortly. | | 13. Upcoming Midyear Reports & Board Reviews | Terence previewed several incoming bodies of work for the committee to audit, including the Security Incident Officer midyear report and the Bug Bounty midyear report. | Action: As June concludes, items will move to the OCTSC review column on the project board. Members must review these submissions. Bernard’s template can be used to draft final reports. | | 14. Tooling Sustainability & Closer | Terence noted the committee is looking for critical ecosystem tools suffering from lack of support. Band 3/4 projects ($2k–$5k) can be funded quickly, but they need one more confirmed project to unlock the next milestone. | Action: Members aware of critical tools in need of funding (e.g., ongoing discussions around tap tools) should submit them for comprehensive review. Meeting adjourned to Discord. | --- # 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-11-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.