4e6a01023b
Some inline `<style>` tags were temporarily added to the documentation because the documentation-stylesheets where not yet updated to the latest version (see https://github.com/docker/docker/pull/11231 and https://github.com/docker/docker/pull/11229#issuecomment-77698868). This removes those temporary `<style>` tags. depends on #11230 (https://github.com/docker/docker/issues/11230) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1.4 KiB
page_title: Understand how to contribute page_description: Explains basic workflow for Docker contributions page_keywords: contribute, maintainers, review, workflow, process
Understand how to contribute
Contributing is a process where you work with Docker maintainers and the community to improve Docker. The maintainers are experienced contributors who specialize in one or more Docker components. Maintainers play a big role in reviewing contributions.
There is a formal process for contributing. We try to keep our contribution process simple so you'll want to contribute frequently.
The basic contribution workflow
In this guide, you work through Docker's basic contribution workflow by fixing a
single white-belt issue in the docker/docker repository. The workflow
for fixing simple issues looks like this:
All Docker repositories have code and documentation. You use this same workflow for either content type. For example, you can find and fix doc or code issues. Also, you can propose a new Docker feature or propose a new Docker tutorial.
Some workflow stages do have slight differences for code or documentation contributions. When you reach that point in the flow, we make sure to tell you.
Where to go next
Now that you know a little about the contribution process, go to the next section to find an issue you want to work on.