> 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/05-14-2026-meeting-minutes.md). # (05/14/2026) Meeting Minutes ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | Term (End) | | ------------------------ | ---------- | ---------- | ----------------- | ------------ | | 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 | No | 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 | | Pawel Jakubas | Yes | Member | Y | April 2028 | | Olivier Mwatsimulamo | Yes | Member | Y | April 2028 | | Bora Oben | No | Member | Y | April 2028 | | Dominik Hinkleman | Yes | Member | Y | April 2028 | | Kambale Mechack Elie | Yes | Member | Y | April 2028 | Community/Other Attendees * Dan Baruka * Emmanuel Titi * Harun Mwangi * Mike Hornan * Uche Obasi **Recording:** [Open Source Committee (Intersect) - 2026/05/14 - Recording](https://drive.google.com/file/d/158yjG60hJnYXIj7Gq07jTv9MdZh8MZss/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/05/14 - Transcript](https://docs.google.com/document/d/155N0sPlHzSzITT06Jijo3m97iWcZvlv7AWCKrM4MF3M/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/05/14 – Chat Transcript](https://drive.google.com/file/d/1MJ2eyIXujqy6fIC9ZQVNmJHeNtPC5j4y/view?usp=sharing) ## Intros Bora: TBD\ Bernard: TBD\ Dominik: OSC member, BD & Many hats at Inferara\ Georg: past OSC member, outgoing OSC Lead\ Jordan: TBD\ Kambale: TBD\ Olivier: Goma Hub Member, Milestone Reviewer in Project Catalyst, elected MCC and Open Source Committee (April 2026 elections)\ Pawel: Senior Software Eng, Cardano Foundation\ Reshma: OSC voting member\ Sebastian: OSC member, Andamio co-founder\ Tex: Open Source Program Manager, Intersect Staff, Open Source Committee Secretary\ Udai: Member OSC and TSC, CEO- AIQUANT Technologies ## Agenda 5.14.26 * Welcome New Committee Members * Intro/Outro from Georg * Developer Advocate Check In * Bug Bounty Program Payouts * OSS Minneapolis final updates * Meeting Cadence, change? * Chair Elections & Process * Sebastian Pabon (internal nominee for Chair) * Request from Newly Elected for Vice Chair candidates * Committee Member Onboarding Sessions * Google Drive/ClickUp Overview * Maintainer Retainer Program Updates/Actions * Open Forum ## Decisions/Actions **Decisions** * **Retention of Meeting Cadence:** The committee decided to keep the current meeting day and time unchanged, as it remains reasonable for members in different time zones (such as Japan) and moving it would cause further scheduling conflicts. * **Reduction of Program Scope:** The committee finalized the decision to return the funding for two programs—Code for Us and the Summer of Code—effectively reducing the active portfolio from ten programs to eight. * **Nomination for Committee Chair:** Sebastian was put forward and recommended by Terence to step up as the next committee Chair, with official confirmation scheduled for early June. **Actions** * **Submit Discord Votes (All Members):** Members need to cast their approval or denial votes on the two active Discord polls regarding the Bug Bounty program payouts and the onboarding of eight new maintainers within the 24-hour window. * **Pick Up Event Badges (OSS Minneapolis Attendees):** Attendees arriving in Minneapolis on Sunday must prioritize picking up their event badges before 6:00 PM Central Time to avoid lines on Monday morning. * **Review Tooling Sustainability Applications (All Members):** The committee needs to actively drive and approve applications for the Tooling Sustainability program before the September 1, 2026 contract deadline to prevent funds from being returned to the treasury. * **Onboard New Members to Tools (Terence):** Terence needs to send ClickUp workspace invitations to the new committee members (specifically Dominic) and guide them through the Google Drive setup. * **Evaluate Maintainer Applications (All Members):** Committee members must review, score, and shortlist the community maintainer applications in ClickUp by early next week, with interviews to be scheduled and conducted the following week. * **Process Outstanding Milestones (Terence):** Terence needs to process and clear the outstanding first and second milestones for the five remaining pre-pilot maintainers under the Maintainer Retainer program. | Topic | Discussion | Notes | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Meeting Logistics & Attendance | Emmanuel requested to speak early in the meeting due to a scheduling conflict with another call in 15–20 minutes. Terence noted difficulty sharing the ClickUp desktop application due to having too many open tabs. | Members briefly greeted each other. Georg noted his return from recent travels. | | 2. Committee Chair Facilitation | Terence clarified his role as Open Source Program Manager and Secretary, explaining that while he actively manages agendas and meeting flow to keep things moving, he will collaborate with and hand over facilitation to the newly elected Chair once chosen. | Terence emphasized that he will not overstep the Chair's bounds unless necessary to maintain meeting progress. | | 3. Member Profiles & Conflicts of Interest | Terence shared an introduction template in the chat for committee members to declare their current organizational positions, affiliations, and any potential conflicts of interest. | These details are included in the meeting minutes to transparently flag when a member should abstain from specific votes. | | 4. Committee Introductions | Outgoing lead Georg invited the incoming committee members to introduce themselves, share their location, and state what they hope to accomplish. | \* Dominic: Based in Japan; hopes to support open-source projects and learn.\* 8Pro (Kalak): Based in Uganda; focused on contributing to the Cardano ecosystem.\* Olivier: Based in DRC; active in Intersect since early stages, front-end dev at GMA Cardano Hub.\* Pawel: Based in Poland; veteran since 2018 working for Cardano Foundation. Interested in critical infrastructure and funding projects to prepare for AI agentic programming. | | 5. Developer Advocate Updates | Emmanuel provided updates for the last two weeks, highlighting work on the Developer Experience Survey report and preparations for an upcoming physical workshop in Nairobi. Dan shared updates on fixing the developer pathway based on feedback. | \* Emmanuel's workshop will train participants to set up relay and block-producing nodes in under two hours across various operating systems.\* Dan noted that PR merges for the developer portal should happen this week. Bora (Cardano Foundation) is the main feedback provider. | | 6. Open Source Program Overview | Georg provided a historical overview of the committee's work and the "paid open source model" funded by the treasury ($3M USD / 6M ADA). He noted that some programs (like mentorship) were returned due to capacity limits, but successful ones are being handed over. | Georg challenged the new committee to listen to the community, identify program flaws, take ownership of specific areas, and focus heavily on improving successful initiatives. | | 7. Bug Bounty & Maintainer Retainer Approvals | Terence called for committee votes on active Discord polls regarding Bug Bounty program payouts and the onboarding of eight new maintainers. Mike (Security Officer) requested quick approvals to clear an accumulation of pending invoices. | The Security Council (including experts like Giorgio, Kevin, John, Carlos, and Andrew) has already vetted and approved the bug bounty amounts. Polls are set to close in 24 hours. | | 8. Open Source Summit Minneapolis | Terence provided a final travel update for the upcoming event starting Monday. Attendees representing Intersect and the community include Terence, Bora, Marco, Georg, Jordan, Sebastian, James M., Ian, Marsha, Sam, James D., and Adam. | \* Attendees arriving Sunday were advised to pick up badges before 6:00 PM Central Time to avoid lines Monday morning.\* The team will wear custom Cardano-branded shirts on Tuesday to maintain an on-brand presentation. | | 9. Meeting Cadence Review | Terence opened the floor to adjust the meeting time or day, specifically evaluating conflicts with the Civics Committee and accommodating Dominic's timezone in Japan. | Dominic confirmed that the current starting time (10:00 PM local time for him) is reasonable. The committee decided to keep the meeting time unchanged. | | 10. Chair & Vice Chair Election Process | Terence recommended Sebastian to step up as the next Chair, noting that Sebastian has agreed to the role. The official election will align with other Intersect committees in early June. The committee will also look for a Vice Chair from the newly elected pool. | \* New members serve a 2-year term; the prior term group can stay for up to 18 months (until April).\* The Vice Chair role requires additional time commitments to manage documents and stay active in Discord. | | 11. ClickUp Program Tracking | Terence reviewed the portfolio status in ClickUp. The Accelerator and Project Support Services are pending funding access. Code for Us and Summer of Code are being formally returned (20% of the original 10-program scope). | Active programs remaining: Maintainer Retainer, Tooling Sustainability, Bug Bounty, Developer Advocate, Security Incident Management, and Travel/Events. | | 12. Tooling Sustainability Budget | Terence noted a lack of applications for the Tooling Sustainability program despite having a substantial remaining budget. | Critical Deadline: Funds for tooling projects must be signed under contract by September 1, 2026, or the remaining funds will be returned to the treasury. | | 13. Maintainer Retainer Milestones | Terence announced that funding has hit the Andamio treasury for the pre-pilot. Maintainer Darlington successfully collected his first milestone. Terence is working on clearing milestones 1 and 2 for five other maintainers. | Sebastian confirmed that the program’s transactions and fund flows can be viewed transparently on-chain via the Andamio application without needing a token. | | 14. Community Maintainer Selection Process | Reshma presented a slideshow detailing the evaluation process for current applications in ClickUp. Criteria include project relevance, contribution evidence, maintainer experience, CI/CD and security awareness, and community engagement. | \* Target: Complete initial scoring and candidate shortlisting early next week.\* Interviews: Planned for the following week, with a goal to finalize selections by the end of May. | | 15. Security Bug Disclosures | Mike provided technical context on three resolved low-severity (Severity 4) vulnerabilities awaiting payout approval: a symlink issue in Cardano CLI, an off-chain metadata fetching issue in DB Sync, and a DMQ node fix. | Sebastian recommended that committee members read Mike's Q1 security report in Discord and supported the implementation of regular monthly security reporting. | --- # 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/05-14-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.