> 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-march-11-2026.md).

# Meeting Minutes - March 11, 2026

## Attendees:

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

Community/Other Attendees

* Musa Ridwan Itopa

**Recording:** Unavailable

**Transcript:** Unavailable

**Chat Transcript:** [DevEx Innovation WG Meeting – 2026/03/11 – Chat Transcript](https://developers.cardano.org/)

## Agenda 3.11.26

* TBD
* NOTE: Minutes are limited due to an issue in capturing the recording.

## Decisions/Actions

**Decisions**

* **Issue Filing/Tracking:** The group reached a consensus to use [developers.cardano.org](http://developers.cardano.org) as the main place for Issue reporting.
* **Communication/Discussion of Issues:** TWhen discussing which issues should be filed, or refining the focus of certain topics to address, the conversations can take place in ’Discussions’ under [developers.cardano.org](https://github.com/cardano-foundation/developer-portal/discussions) or [devex.intersectmbo.org](https://github.com/IntersectMBO/developer-experience/discussions)

**Actions**

* **Agenda Call:** Tex, Bora, and Robertino will meet to establish an actionable Agenda based upon the first two sessions, aligned with the thoughts discussed in the meeting and on the Miro Board.

| Topic                            | Discussion                                                                                                                                                          | Notes                                                                                                                                                         |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| TBD                              | <p><br></p>                                                                                                                                                         | <p><br></p>                                                                                                                                                   |
| TBD                              | <p><br></p>                                                                                                                                                         | <p><br></p>                                                                                                                                                   |
| TBD                              | <p><br></p>                                                                                                                                                         | <p><br></p>                                                                                                                                                   |
| Issue Reporting                  | Feedback about changes to improve Developer Experience should be filed as issues. They should primarily be stored on the Developer Portal repository.               | Issues ‘could’ be reported elsewhere, but those filed under the Dev Portal should be treated as actionable.                                                   |
| Discussion of potential ‘Issues’ | Issues are filed under the Dev Portal repo to reduce fragmentation, discussions of which issues to file should be accessible and could happen in any channel\*      | The preference is to direct discussion of potential issues to the ‘Discussions’ page under Dev Portal or Devex (Intersect) repos.                             |
| Functional Agenda                | The effective ‘leads’ of this innovation initiative from the founding entities agreed to meet separately ahead of the next meeting to formalize a dedicated agenda. | The second session was primarily a discussion about Developer Experience concerns. In order to maintain quick improvements, an actionable agenda is required. |


---

# 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-march-11-2026.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.
