> For the complete documentation index, see [llms.txt](https://opensourcecommittee.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://opensourcecommittee.docs.intersectmbo.org/working-groups/cardano-devex-innovation-working-group/meeting-minutes/meeting-minutes-april-15-2026-3.md).

# Meeting Minutes - May 27, 2026

## Attendees:&#x20;

| Name                     | Attendance | Role/COI                     |
| ------------------------ | ---------- | ---------------------------- |
| Terence ‘Tex’ McCutcheon | Yes        | Lead/Secretary               |
| Bora Oben                | No         | Developer Advocate - CF      |
| Dan Baruka               | No         | Developer Advocate Intersect |
| Emmanuel Titi            | Yes        | Developer Advocate Intersect |
| Harun Mwangi             | No         | Developer Advocate Intersect |
| Uche Obasi               | No         | Developer Advocate Intersect |
| Sebastian Pabon          | Yes        | OSC Member                   |
| Darlisa Consoni          | No         | Ecosystem Engineering - CF   |
| Robertino Martinez       | Yes        | Product Owner - DevEx IOG    |

Community/Other Attendees

* Josefine Birkigt

**Recording:** [Cardano DevEx Innovation WG - Feedback Session - 2026/05/27 - Recording](https://drive.google.com/file/d/17mpx3CfAsX5WM6qyNgd-NntzfA8ibqlu/view?usp=sharing)

**Transcript:** [Cardano DevEx Innovation WG - Feedback Session - 2026/05/27 - Transcript](https://docs.google.com/document/d/1UsiqqtaE-xOdCQwg7B66Bf5i2Nb8qW6KqeuMxGiU3mA/edit?usp=sharing)

## Agenda 5.27.26

* Catch Up
* Feedback Session Scheduling

## Decisions/Actions

**Decisions**

* **Workshop Scheduling:** Agreed to pass on the mid-June dates due to scheduling conflicts and tentatively set the upcoming outreach workshops for June 30th and July 1st to avoid the summer holiday season.
* **Session Structure:** Decided to structure the community feedback sessions as recorded events with a strict 30-second to 1-minute time cap per person to keep the input concise and actionable.
* **Primary Communication Channel:** Selected Discord as the official platform for ongoing team communications and thread updates.
* **Open Source Collaboration:** Agreed to make all Developer Portal documentation discussions and proposal implementations entirely public on GitHub to allow anyone in the ecosystem to review, comment, and pick up issues.

**Actions**

* **Terence:** Document the official meeting minutes and draft a structured, actionable plan for the upcoming developer workshops.
* **Terence:** Share the workshop planning document with the team via the newly created Discord thread for feedback and iteration.
* **Robertino:** Begin the hiring process to build a dedicated team of engineers to implement the approved proposal changes, as current engineering resources are fully allocated elsewhere.
* **Team (All):** Review the placeholder invites for June 30th and July 1st and iterate on the workshop strategy document over the next week.

| Topic                                         | Discussion                                                                                                                                                                                                                                                                             | Notes                                                                                                                                                                                                          |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Open Source Summit Recap                   | Terence and Sebastian shared their feedback regarding the open-source event in the US. The group consisted of 13 people. While there was a heavy emphasis on AI throughout the event, it did not take away from the core open-source discussions.                                      | Attendees found the conference to be an exceptional educational experience and a great platform for exposing their ongoing work.                                                                               |
| 2. Marketing Reset & Developer Outreach Goals | Terence noted that the marketing goals for the developer outreach sessions were missed and suggested resetting the strategy. The primary goal remains establishing an open space for any Cardano ecosystem developer to share their friction points and real-time development hurdles. | Rather than relying solely on internal data or Miro boards, gathering direct confirmation and feedback from the community is deemed critical.                                                                  |
| 3. Structure of Feedback / "Rant" Sessions    | Josefine raised questions on how to effectively manage and capture the feedback without it turning into a chaotic rant session. Terence proposed hosting a recorded session where speakers are capped at 30 seconds to one minute to state their core developer experience problem.    | Appropriate structural controls must be defined to keep the feedback constructive, concise, and translatable into actionable items.                                                                            |
| 4. Communication & Marketing Channels         | Josefine emphasized the importance of clearly communicating what will happen to the developers' feedback after it is collected. She confirmed that multiple reach-heavy channels are readily accessible to market the upcoming initiative.                                             | Marketing channels identified include the Luma calendar (\~1,000 subscribers), Cardano Next, Reddit, the Cardano Forum, and the developer Telegram channel.                                                    |
| 5. Proposal Approval Congratulations          | Emmanuel joined the call and congratulated Robertino on his team's proposal successfully passing, noting it resolves a long-standing ecosystem issue. Robertino shared that the process was incredibly stressful up until four hours before the deadline.                              | Terence noted that he has fully returned from his trip and successfully re-established his internet connection.                                                                                                |
| 6. Asynchronous Feedback via GitHub           | Robertino suggested providing an asynchronous, written feedback option via GitHub for developers who prefer reading and commenting on threads over attending live meetings or workshops.                                                                                               | Providing a written pipeline ensures a broader and more inclusive segment of the developer ecosystem is captured.                                                                                              |
| 7. Feedback Consolidation Workflow            | Terence outlined a workflow where live and written feedback is synthesized into a consolidated list, which is then converted into actionable issues or discussion threads on the Developer Portal.                                                                                     | The goal is to build out general topics into specific issues that external contributors or community members can eventually pick up.                                                                           |
| 8. Funding, Bounties, & Incentives            | Josefine inquired about using bounties to incentivize developers to fix these issues. Terence explained that the original "Summer of Code" and "Code for Us" program budgets had to be returned to the treasury due to management bandwidth limitations.                               | Although financial bounties are unavailable right now, contributing provides developers with an excellent resume builder and elite visibility to Cardano Foundation partners and Intersect enterprise members. |
| 9. Alignment with Robertino's Proposal        | Sebastian raised the need to align the team's ongoing developer advocacy goals with the workflow of Robertino’s newly approved proposal.                                                                                                                                               | Bora (absent) was identified as another key leg of these technical conversations who will be actively collaborating moving forward.                                                                            |
| 10. Developer Portal Documentation & Hiring   | Robertino explained that all documentation changes and newcomer paths will be open for public discussion on GitHub. He also noted that he needs to hire a brand-new team of engineers to implement these changes, as his current engineering resources are fully allocated.            | This documentation shift heavily overlaps with the core mission of developer advocates looking to improve resources for incoming developers.                                                                   |
| 11. Cross-Organizational Collaboration        | Sebastian pointed out the historical difficulty of working seamlessly across Intersect, Cardano Foundation, and independent entities. He highlighted Robertino’s proposal as a perfect catalyst to establish closer internal alignment.                                                | Robertino welcomed the idea of drawing up a written agreement to explicitly define responsibilities and integrate diverse skill sets across the ecosystem.                                                     |
| 12. Workshop Scheduling                       | The team debated ideal dates to accommodate multiple time zones (Asia and US), proposing morning and afternoon slots. Mid-June dates (16th–17th) were ruled out due to existing scheduling conflicts for Josefine and others.                                                          | The team agreed to set calendar placeholders for June 30th and July 1st to ensure high attendance before the summer holiday season starts.                                                                     |
| 13. Communication Channels & Next Steps       | Terence confirmed he would document the actionable plan, distribute the meeting minutes, and share a working document. The team agreed to use Discord as their primary communication hub moving forward.                                                                               | Terence created and tagged attendees in a dedicated Discord thread to maintain momentum asynchronously.                                                                                                        |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://opensourcecommittee.docs.intersectmbo.org/working-groups/cardano-devex-innovation-working-group/meeting-minutes/meeting-minutes-april-15-2026-3.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
