> 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/project-support-services.md).

# Project Support Services

### Request for Project Support: [Support Services Survey](https://forms.clickup.com/9015279944/f/8cnmga8-13635/JABH2WVEOIS8Q4UAGU)

This survey is designed to assist the Open Source Office in determining an appropriate supply timeline and to seek to provde support to as many projects as possible.

### Background:

In the ever-evolving landscape of Cardano, open source projects serve as catalysts for innovation, driving progress and collaboration. However, the intricacies of managing these projects can present formidable challenges. Recognizing this, Intersect's Open Source Office (OSO) stands ready to provide crucial support services.

### Definition:

As the cornerstone of Cardano's open source ecosystem, the OSO acts as a beacon of support and guidance for project teams. Serving as a central hub, it offers a diverse array of resources and expertise to facilitate effective project management. From navigating licensing requirements to fostering community engagement, the OSO empowers teams to maximize the impact and sustainability of their open source endeavors.

### Open Source Office (OSO) Support Services

Intersect’s Open Source Office offers a strong backbone of services to Cardano open source projects, built around the goal of sustaining most project needs outside of just code management and technical decisions. We will offer an enhanced set of services via professional staff that cultivate the maturity and increased adoption of Cardano related open source projects.\
\
We take a data driven approach to working with our project and maintainer community; we actively survey to improve our services and community satisfaction on top of featuring services in our community spotlight/essential cardano/cardano 360.

These services will be offered as part of community stability, but do not replace developers on the projects themselves and are never meant to be in the critical path of a project release or a full time resource. Our goal in providing these shared services is to cultivate projects on Cardano and the builders graduating and incubating projects, offering sandbox projects in the space to grow into incubating projects.

<figure><img src="https://493748844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLBdnzp0eZpGri9sVpseI%2Fuploads%2F25ZxtwHOM8IXWdtuHZL0%2Fimage.png?alt=media&amp;token=be595f6d-e5a5-4381-ba0d-9adbb0819846" alt=""><figcaption></figcaption></figure>

<br>


---

# 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://committees.docs.intersectmbo.org/intersect-open-source-committee/about/open-source-office-oso/project-support-services.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.
