# May 4 2026 ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | | ---------------------------------------------------- | ---------- | ----------------------------- | ----------------- | | [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N | | Jack Briggs | No | Executive Director | Y | | Sheldon Hunt | Yes | Community Member Seat | Y | | Fred Tanaka | No | Community Member Seat | Y | | Kristijan Kowalsky | Yes | Community Member Seat | Y | | Jose Miguel de Gamboa | Yes | Community Member Seat | Y | | Georg Link | No | OSC Chair | Y | | Samuel Leathers | Yes | Product Chair | Y | | Maureen Wepngogn | Yes | MCC Chair | Y | | Megan Hess | Yes | CBC Chair | Y | | Kevin Hammond | Yes | TSC Chair | Y | | Tim Harrison | No | GMC Chair | Y | | Nicolas Cerny | No | CCC Chair | Y | | Lorenzo Bruno | Yes | Head of Product & Membership | Y | | Larisa Mcfarlane | Yes | Head of Ecosystem & Community | Y | | Nick Cook | No | Head of Operations (Interim) | N | | Bosko Majdanac | Yes | Secretary of TSC | N | | Abhik Nag | Yes | Secretary of MCC | N | | Lloyd Duhon | Yes | Secretary of Budget Committee | N | | Terence McCutcheon | Yes | Secretary of OSC | N | | Lara Bonasorte | No | Secretary of GMC | N | | Thomas Lindseth | Yes | Secretary of CCC | N | ### Additional Attendees: Laura Mattiucci - Vice Chair of GMC Kyle Solomon - Vice Chair of Product Committee \ Agenda: ------------- * Committee Updates * Committee Election Update * ByLaws Voting * Code of Conduct - Draft Proposal ## Discussion/Actions ### 1. Opening & Agenda The meeting opened with attendance confirmation and quorum established. The agenda focused on committee updates, budget process progress, committee elections update, governance tooling status, and discussion on improving the code of conduct process and related governance structures. *** ### 2. Committee Updates * Technical Steering Committee (TSC) confirmed submission of its budget proposal, covering support for SIP editors, parameter committee, hard fork working group, technical event participation, and a proposal review pilot for 2027. The Van Rossum hard fork is progressing as planned, with preview expected to upgrade shortly, followed by pre-production testing. Mainnet submission is targeted for late May, pending successful testing and community readiness. The Plutus cost model update is also progressing, with sequencing aligned to upcoming governance actions. Forward-looking discussions include post-quantum strategy and identified risks in linear fee mechanisms. * Product Committee noted its proposal has been submitted and is awaiting feedback, with further progress dependent on the outcome of ongoing committee elections. * Open Source Committee (OSC) confirmed its proposal is live and highlighted ongoing efforts to support additional proposals (including Civics). Communication and visibility of proposals are expected to increase in the coming period. * Budget Committee reported approximately 14 proposals submitted so far via the platform, with additional submissions expected before the deadline. Engagement is currently limited but anticipated to increase once the submission window closes. Members were encouraged to begin reviewing and commenting on proposals. * Growth & Marketing Committee (GMC) discussed its role in evaluating and potentially endorsing proposals, with alignment that committees can formally express support or concerns, provided this is done through agreed internal processes (e.g., committee vote and coordinated response). Ongoing discussions include marketing proposals and broader ecosystem alignment. *** ### 3. Budget Process & Proposal Engagement The submission phase is actively progressing, with growing proposal volume and expectations of increased engagement. Key points: * Committees are encouraged to actively review and comment on proposals during the feedback window * Formal committee responses should be coordinated and approved internally before submission * Guidance for committees on how to review and respond to proposals is being prepared and will be shared shortly *** ### 4. Committee Elections Update An update was provided on the committee election results delay: * Results publication was postponed by approximately 24 hours due to additional audit checks * No changes were made to the voting process itself; improvements were implemented prior to the election * Additional validation steps are being conducted to ensure integrity and accuracy of results It was emphasized that: * Maintaining trust and correctness of results is a priority over speed * Communication to the community will clarify the reason for the delay and reinforce transparency *** ### 5. Governance Tooling (GovTool) Update An update was shared regarding GovTool availability and stability: * Recent issues were identified, likely related to infrastructure dependencies (e.g., DB sync), though further investigation is ongoing * The tool is currently operational but may experience instability, particularly with upcoming network upgrades * GovTool remains unfunded and lightly maintained, with limited active development support Key considerations: * Long-term sustainability remains uncertain * Open source contributions and potential funding pathways (e.g., via OSC) are being explored * Community adoption will be a key factor in determining future support *** ### 6. Code of Conduct & Complaints Process A discussion was held on improving the code of conduct enforcement process, following recent incidents. Key points: * Existing guidance is distributed across multiple documents (Code of Conduct, bylaws, membership agreement) * A need was identified for a more clear, structured, and documented process Proposed approach: * Establish a dedicated review body to handle complaints and provide recommendations * Maintain a clear intake channel (e.g., formal email submission) * Ensure confidentiality, due process, and proper record-keeping * Define structured procedures, including categorization of issues and corresponding actions It was noted that: * This body would likely recommend actions, with final decisions (in serious cases) made by the Board * Further work is required to define roles, decision-making structure, and safeguards (including handling conflicts of interest and malicious complaints) Next steps: * Proposal to be refined and shared for async discussion and vote * Detailed process and governance framework to be developed by the proposed body *** ### 7. Bylaws Update (Reminder) A reminder was shared that updated bylaws are ready following prior legal review: * Changes are required to ensure alignment with Wyoming legal requirements * A member-wide vote will be required to approve the updated bylaws Next steps include: * Sharing a clear summary of changes and supporting materials * Defining voting criteria and timelines * Preparing the proposal for formal member voting in the coming weeks *** ### 8. Actions & Next Steps * Share guidance for proposal review and committee engagement * Communicate committee election delay with clear rationale * Review and vote on proposed code of conduct review body * Support development of a structured complaints process --- # 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://steeringcommittee.docs.intersectmbo.org/committee-meeting-notes/2026-meeting-notes/may-4-2026.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.