# The Open.HD Ecosystem

> ⚠️ **This documentation is outdated!** A current version is available at [openhdfpv.org](https://openhdfpv.org)
>
> [📖 **View Updated Version of This Page** →](https://openhdfpv.org)

***

**Github, Docker, Drone.io, Cloudsmith & Co.**

Github is where all of our code is stored. "Master" branches are the new future 3.0 OpenHD and is unfinished. 2.0 branches are where the current working code resides.

For distribution Open.HD makes use of a build-pipeline in order to speed up the build process and automate some tasks that otherwise would have to be done via means of tedious manual commands.

The pipeline starts with Github repository ([Open.HD · GitHub](https://github.com/OpenHD)).\
Once new code gets comitted/merged drone.io ([Drone.io](https://cloud.drone.io/)), which is an "*Open source continuous integration platform built on Docker*" starts taking over. Drone.io uses configuration \*.yml files in each github repository and builds a package from a script, packaage.sh, found in the same github repository.

Drone.io if successful pushes the Open.HD packages to [cloudsmith](https://cloudsmith.io/repos/), which is a universal package management solution, allowing creation, storeage, and shareing ready to install Linux packages.

In summary, if you want to try new code you commit to github, it gets merged, docker builds it automatically with drone.io, new package appears in cloudsmith. Of course it is recommended you build on your local machine and test any code prior to committing to github.

{% hint style="info" %}
untagged commits go to "testing" cloudsmith packages only
{% endhint %}

{% hint style="info" %}
In the past, travis was also used to package openhd 2.0
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://openhd.gitbook.io/open-hd/master/developer-corner/the-openhd-ecosystem.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.