From b4d7b0f8657cd29147dd3215876b9f739ead7097 Mon Sep 17 00:00:00 2001 From: Maxim Kulkin Date: Wed, 25 Mar 2015 15:47:15 -0700 Subject: [PATCH] Explain advanced contribution workflow more Explain why advanced contribution workflow have to be so complex Signed-off-by: Maxim Kulkin --- docs/sources/project/advanced-contributing.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/sources/project/advanced-contributing.md b/docs/sources/project/advanced-contributing.md index df5756d9d7..0c9b5d1ce8 100644 --- a/docs/sources/project/advanced-contributing.md +++ b/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.