# Contribute We believe everyone has something valuable to contribute, whether you’re a coder, a writer, or a tester. Here’s how and why you could get involved: - **Why join us**: Work with like-minded people, grow your skills, connect with diverse professionals, and make a difference. - **What do you get**: Personal growth, recognition for your contributions, early access to new features, and the joy of seeing your work appreciated. - **Start early, start simple**: Dive into code contributions, improve documentation, or be among the first testers. Your presence matters, regardless of experience or the scale of your input. ## Standards and expectations **Workshop** is an emergent project stewarded by the DevEx department at Canonical. Before you start, familiarize yourself with two documents: - The [Ubuntu Code of Conduct](https://ubuntu.com/community/docs/ethos/code-of-conduct) sets the standard for respectful collaboration across the community. - The [license](https://github.com/canonical/workshop/blob/main/LICENSE) governs how the project’s code is used and distributed. ## Ways to contribute Pick the path that matches the work you want to do: - [Contribute to development](https://ubuntu.com/workshop/docs/contributing/development.md#contributing-development) takes a code change from a local environment through to a merged pull request. - [Contribute to this documentation](https://ubuntu.com/workshop/docs/contributing/documentation.md#contributing-documentation) follows the same arc for changes to this documentation. - Report a bug or share feedback through the [issue tracker](https://github.com/canonical/workshop/issues). Maintainers can find the release process, automation, and repository tooling in [Maintain the project](https://ubuntu.com/workshop/docs/contributing/maintenance.md#contributing-maintenance). ## Feedback and issues Before opening a new issue, search the [existing issues](https://github.com/canonical/workshop/issues) to avoid duplicates and to see whether the topic is already being worked on.