## Why contribute? ### Copyright stays with you Unlike some other projects, we intentionally do not use a contributor agreement that would give us exclusive rights to your contributions. The copyrights to VyOS source code and documentation remain shared between all contributors, so that no one (including its current maintainers) can make a proprietary fork. ### We have rewards Maintaining an LTS version is a hard, delicate, high-responsibility work. Being a maintainer means not being able to refuse to work on the hard tasks. We keep prebuilt LTS images behind a paywall for that reason, but we are ready to share our work with everyone who helps us move the project forward. This includes everyone who contributes code, tests latest builds, writes documentation, or promotes VyOS in the social media or at live events. Read about our [contributor subscriptions](/get/contributor-subscriptions) to review eligibility guidelines and [fill the application form](/get/contributor-subscriptions#application-form). We also have [badges](https://www.youracclaim.com/organizations/vyos/badges)!

## Where to start ### Contributing to the code * Read the [introduction to VyOS development](https://docs.vyos.io/en/latest/contributing/development.html). * Browse [open tasks](https://vyos.dev/maniphest/query/YqwCUwoj7wWx/#R). ### Contributing to the documentation * Fork the [vyos-documentation](https://github.com/vyos/vyos-documentation/) repo. * Read the [guidelines](https://docs.vyos.io/en/latest/documentation.html). ### Testing latest builds * Get a [nightly build](/get/nightly-builds). * Reports bugs in [Phabricator](https://vyos.dev/maniphest). ### Spreading the word * Write about VyOS in your own blog or website. * Write about VyOS and share our posts on social media. * Speak about VyOS at conferenced and meetups.