## Contributing to Tutorials ##

Thank you so much for your interest in contributing to [Docker](https://docker.com) tutorials. Docker has open source in its DNA, and has always worked closely with the community.

Just a few quick things to be aware of before you get started.

We welcome issues and pull requests for fixing a problem with an existing tutorial. We are not accepting new tutorials. If you want to contribute new tutorials, please consider contributing to [training.play-with-docker.com](https://training.play-with-docker.com) in this repository: [https://github.com/play-with-docker/play-with-docker.github.io](https://github.com/play-with-docker/play-with-docker.github.io).

Anything you contribute will be under an Apache license. Docker will choose which tutorials to accept and reject, and will be able to take any tutorials here and put them in Docker documentation. Likewise, anything posted here may be forked by anyone on GitHub.

We will be following the lightweight version of the Docker contribution policies and procedures as explained in
- [Docker documentation](https://docs.docker.com)
- The [Docker engine repo](https://github.com/moby/moby/blob/master/CONTRIBUTING.md).

This largely boils down to [signing your PRs](https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work), following the Docker [trademark guidelines](https://www.docker.com/trademark-guidelines), and following the community guidelines.