mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
Explain advanced contribution workflow more
Explain why advanced contribution workflow have to be so complex Signed-off-by: Maxim Kulkin <mkulkin@mirantis.com>
This commit is contained in:
parent
e6b7d93072
commit
b4d7b0f865
1 changed files with 13 additions and 0 deletions
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue