> 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/about/open-source-office-oso/developer-advocate-program/developer-advocate-cohort-1-1/cohort-2-deliverables.md).

# Cohort #2 Deliverables

{% file src="/files/LnqIeiS6dm9sKUVrZpV8" %}

#### General Deliverables

1. **Developer Experience Working Group**

**Description:** Participate/Lead Developer Experience working group.This task includes establishing the meeting cadence as well as seeking participation. Developer Advocates have received a block on the OSC agenda to provide regular updates.

**Acceptance Criteria:** Reports of Developer Experience Working Group progress should be provided to the Open Source Committee every four weeks, alternating developer advocate monthly.

Keep a record of Developer Experience Pain points to be addressed in OSC’s Open Source Strategy, including a plan for improvement. The Developer advocates to produce one common document that can be shared with the OSC.

Each Developer Advocate will create draft documentation for various Core Cardano repositories. These documents can be reviewed by OSC, TSC, and relevant Technical Working Group members for inclusion.

When: Q4 2025, Q1 2026, Q2 2026

2. **Onboarding New Developers**

**Description:** Developer Advocates will begin to connect with developers from the Community, encourage attendance to Dev Ex and Technical working groups to bring developers to Core Cardano. Developer Advocates are also expected to maintain documentation specific to development on Cardano in the developer-experience repository under the IntersectMBO organization on GitHub.

**Acceptance Criteria:** The Developer advocates will provide a list to the OSC of how many new developers they have onboarded to the working groups aiming for a minimum of 2 new developers per DA during each quarter, measurable against the contribution tracking and/or social media highlights.

Visible documentation specific to development on Cardano in the developer-experience repository under the IntersectMBO organization on GitHub. Help build learning materials or suggestions to the existing list of materials provided by OSC or OSO members for onboarding.

When: Q4 2025, Q1 2026, Q2 2026

3. **Meetings**

**Description:** Developer Advocates will establish meeting cadence for Dev Ex working group and 1-1 meetings as needed across multiple channels. Aside from normal check-in and OSC meetings, Advocates are expected to make themselves available to meet and onboard new developers.

**Acceptance Criteria:** The Developer advocate should keep a record of meetings attended to provide to Intersect on request. Conversations within Github discussions, Discord, or Slack are welcomed as sufficient mediums.

Each developer advocate should aim to have a minimum of 2 conversations each quarter with new developers to the ecosystem with the aim of onboarding them into the OSO/OSC/Cardano.

When: Q4 2025, Q1 2026, Q2 2026

4. Community Engagement

**Description:** Advocates will continue to attend various Web3 events, seeking to enrich and improve the developer experience Or each developer advocate helps advance the OSO mission by assisting OSO project support service requests in fulfillment of member engagement of intersect.

**Acceptance Criteria:** The Developer advocate shall endeavor to attend a minimum of two (2) Web3 events during each quarter.

Following attendance, the Developer advocate shall prepare a written report or article, such as a blog post, for review and approval by Intersect. (Upon approval, Intersect reserves the exclusive right to publish the write-up in agreement with the Developer Advocate.)

Virtual and in person events are sufficient for fulfillment of the request.Each Developer advocate will assist in delivery of OSO project support services. (As needed)

When: Q4 2025, Q1 2026, Q2 2026

5. **Feedback and Improvement**

**Description:** Advocates should search for/design future feedback collection tools and forms that are accessible and actionable. This begins with the State of Developer Experience Survey offered in Q1 2025.

**Acceptance Criteria:** Revise 2024 Survey, add/adjust questions (differentiate from CF or sync surveys).

By the end of the first quarter ("Q1 2026"), the Developer Advocates should publish and disseminate results from the survey informing the state of Developer Experience. Provide a written summary, including proposed next steps.

When: Q4 2025, Q1 2026, Q2 2026<br>

#### Specific Deliverables

| **Deliverables**                                            | **Acceptance Criteria**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | **Timeframe for achievement of deliverable**              |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| <p><strong>Goal:</strong> Developer-experience Repo<br></p> | <p>Consistent contribution via Issue management, PRs and Approvals, Discussions, etc. in <https://github.com/IntersectMBO/developer-experience></p><ul><li>Submit at least 3 documentation/project PRs per quarter to the DevEx repo. (Community projects will also be considered in lieu of contributions to Dev-ex)</li><li>Publish a quarterly DevEx changelog showing updates and areas needing improvement. (OSO will publish a copy of updated changelog from developer-experience repo)</li><li>Collect and log 10 pieces of feedback from developers on repo usability.</li></ul> | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |
| **Goal:** Deepen Strategic Collaborations                   | <ul><li>Deliver a partnership mapping report of at least 3 new projects, universities, or orgs engaged.</li><li>Facilitate 2–3 introductory meetings between Cardano projects and potential collaborators.</li><li>Document outcomes in a Strategic Collaboration Log (who was contacted, response, next steps).<br><br></li></ul>                                                                                                                                                                                                                                                        | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |
| **Goal:** Implement Diversity & Inclusion Programs          | <ul><li>Host 1 regional or language-specific workshop per quarter.</li><li>State of Developer Experience Survey and related Translation.</li><li>Draft a D\&I onboarding guide tailored for underrepresented groups. (This can also be achieved by reviewing and enhancing Hitchhikers guide and other related documents)</li></ul>                                                                                                                                                                                                                                                       | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |
| **Goal:** Expand Ecosystem with New Projects                | <ul><li>Produce a “New Projects on Cardano” spotlight report featuring 2–3 projects (quarterly). (Collective Milestone, accompanying video via OSO)<br><br></li><li>Onboard at least 1 project into OSO Project Support Services (or document why they declined).<br><br></li><li>Publish step-by-step build guides for newcomers starting projects on Cardano. (Can also be achieved by improving currently available resources eg: Dev Portal)</li></ul>                                                                                                                                | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |
| **Goal:** Foster Innovation & Technology Advancement        | <ul><li>Run 1 technical experiment/demo per quarter (e.g., tooling improvement, repo showcase, testnet demo). (Bring project/owner into a Dev-ex WG meeting)</li><li>Document 2–3 pain points with proposed solutions in the Developer Experience repo.</li><li>Facilitate 1 feedback session with core contributors to test potential innovations.(Achievable with assistance from OSO/OSC)</li></ul>                                                                                                                                                                                    | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |
| **Goal:** Build a Global Community                          | <ul><li>Organize 1 community event per quarter (IRL or virtual).</li><li>Publish a Community Engagement Report summarizing outreach efforts, attendance, and sentiment.</li><li>Translate and distribute 1 educational resource in a local language.</li></ul>                                                                                                                                                                                                                                                                                                                            | <ul><li>Q4 2025</li><li>Q1 2026</li><li>Q2 2026</li></ul> |


---

# 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/about/open-source-office-oso/developer-advocate-program/developer-advocate-cohort-1-1/cohort-2-deliverables.md?ask=<question>&goal=<endgoal>
```

`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.