github.com/carlanton/docker@v1.8.0-rc1/docs/project/make-a-contribution.md (about)

     1  <!--[metadata]>
     2  +++
     3  title = "Understand how to contribute"
     4  description = "Explains basic workflow for Docker contributions"
     5  keywords = ["contribute, maintainers, review, workflow,  process"]
     6  [menu.main]
     7  parent = "smn_contribute"
     8  +++
     9  <![end-metadata]-->
    10  
    11  # Understand how to contribute
    12  
    13  Contributing is a process where you work with Docker maintainers and the
    14  community to improve Docker. The maintainers are experienced contributors
    15  who specialize in one or more Docker components. Maintainers play a big role
    16  in reviewing contributions.
    17  
    18  There is a formal process for contributing. We try to keep our contribution
    19  process simple so you'll want to contribute frequently.
    20  
    21  
    22  ## The basic contribution workflow
    23  
    24  In this guide, you work through Docker's basic contribution workflow by fixing a
    25  single *beginner* issue in the `docker/docker` repository. The workflow
    26  for fixing simple issues looks like this:
    27  
    28  ![Simple process](/project/images/existing_issue.png)
    29  
    30  All Docker repositories have code and documentation. You use this same workflow
    31  for either content type. For example, you can find and fix doc or code issues.
    32  Also, you can propose a new Docker feature or propose a new Docker tutorial. 
    33  
    34  Some workflow stages do have slight differences for code or documentation
    35  contributions. When you reach that point in the flow, we make sure to tell you.
    36  
    37  
    38  ## Where to go next
    39  
    40  Now that you know a little about the contribution process, go to the next section
    41  to [find an issue you want to work on](/project/find-an-issue/).