> 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/about/paid-open-source-model-posm/cardano-summer-of-code.md).

# Cardano Summer of Code

This program is not currently in development as of Nov.6 2025.

**Decision on Cardano Summer of Code Program**\
Following the Open Source Committee (OSC) meeting on November 6, 2025, the committee has decided not to proceed with the Cardano Summer of Code program. This determination was based on several key factors:

* Resource Constraints: Limited availability of personnel and support to manage the initiative effectively.
* Scope of Work: The program's requirements exceeded current capacity and could jeopardize quality.
* Success Criteria: Established benchmarks for program viability and impact, present a barrier too high for success.

While this program will not move forward in the immediate term, it may be revisited as a potential budget proposal for 2026.

**Focus on Existing Programs**\
With nine other active programs currently underway, the OSC prioritizes the effective implementation of initiatives under the Paid Open Source Model (POSM). This strategic focus ensures sustained progress in core areas without overextension.

**Fund Reallocation**\
All allocated funds for the Cardano Summer of Code—totaling 400,000 ADA—will be returned to the treasury. This process will be handled by the administrator (Intersect) in the near future.\
\
**Impact on Open Source Sustainability**\
As the Cardano Summer of Code was positioned as a peripheral element within the POSM framework, its deferral will not affect the primary open source sustainability activities. Core efforts remain on track and unhindered.\
<https://t.co/1reSLzfP2V>


---

# 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/about/paid-open-source-model-posm/cardano-summer-of-code.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.