p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #11775 from maximkulkin/explain-advanced-contribution-workflow

Browse Source 
Explain advanced contribution workflow more
Upstream-commit: da61228501acf24e651e167efb7b3c25c6bf5548
Component: engine
This commit is contained in:
moxiegirl
2015-04-03 06:41:49 -07:00
parent d2894c5f4b 6b3e5068b8
commit 77e454c28a
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
components/engine/docs/sources/project/advanced-contributing.md
View File

@ -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.