Explorar el Código

Explain advanced contribution workflow more

Explain why advanced contribution workflow have to be so complex

Signed-off-by: Maxim Kulkin <mkulkin@mirantis.com>
Maxim Kulkin hace 10 años
padre
commit
b4d7b0f865
Se han modificado 1 ficheros con 13 adiciones y 0 borrados
  1. 13 0
      docs/sources/project/advanced-contributing.md

+ 13 - 0
docs/sources/project/advanced-contributing.md

@@ -137,3 +137,16 @@ The following provides greater detail on the process:
 
 14. Acceptance and merge!
 
+## About the Advanced process
+
+Docker is a large project. Our core team gets a great many design proposals.
+Design proposal discussions can span days, weeks, and longer. The number of comments can reach the 100s.
+In that situation, following the discussion flow and the decisions reached is crucial.
+
+Making a pull request with a design proposal simplifies this process:
+* you can leave comments on specific design proposal line
+* replies around line are easy to track
+* as a proposal changes and is updated, pages reset as line items resolve
+* Github maintains the entire history
+
+While proposals in pull requests do not end up merged into a master repository, they provide a convenient tool for managing the design process.