Developer docs about existing subtrees. #9246

 425 | +
 426 | +- src/leveldb
 427 | +  - Upstream at https://github.com/google/leveldb ; Maintained by Google, but open important PRs to Core to avoid delay
 428 | +
 429 | +- src/libsecp256k1
 430 | +  - Upstream at https://github.com/bitcoin-core/secp256k1/ ; actively maintaned by Core contributors.

paveljanik commented at 9:17 AM on November 30, 2016:

maintaned -> maintained

 407 | @@ -408,6 +408,34 @@ GUI
 408 |      should not interact with the user. That's where View classes come in. The converse also
 409 |      holds: try to not directly access core data structures from Views.
 410 |  
 411 | +Subtrees
 412 | +----------
 413 | +
 414 | +Several parts of the repository are subtrees of software maintained elsewhere.
 415 | +
 416 | + Some of these are maintained by active developers of Bitcoin Core, in which case changes should probably go

paveljanik commented at 9:18 AM on November 30, 2016:

Why SPC at the beginning? To mark paragraph?

Two spaces?

 419 | +
 420 | + Others are external projects without a tight relationship with our project.  Changes to these should also
 421 | +be sent upstream but bugfixes may also be prudent to PR against Bitcoin Core so that they can be integrated
 422 | +quickly.  Cosmetic changes should be purely taken upstream.
 423 | +
 424 | +Current subtrees include:

MarcoFalke commented at 10:52 AM on November 30, 2016:

Maybe link to https://github.com/bitcoin/bitcoin/tree/master/contrib/devtools#git-subtree-checksh, so we don't have to keep track to update 2 places whenever something changes?