Community driven twister-core

twister p2p blockchain network bittorrent ipv6 microblogging social-network dht decentralized twister-core twisterarmy p2p-network twister-server twister-ipv6

Jaromil 84c3fb07b0 directory re-organization (keeps the old build system) there is no internal modification of any file in this commit files are moved into directories according to established standards in sourcecode distribution; these directories contain: src - Files that are used in constructing the executable binaries, but are not installed. doc - Files in HTML and text format that document usage, quirks of the implementation, and contributor checklists. locale - Files that contain human language translation of strings used in the program contrib - Files contributed from distributions or other third party implementing scripts and auxiliary programs		14 years ago
contrib	move gitian descriptor file	14 years ago
doc	directory re-organization (keeps the old build system)	14 years ago
locale	Allow UPnP mapping when USE_UPNP is defined and miniupnpc is installed at build time(statically linked).	14 years ago
share	directory re-organization (keeps the old build system)	14 years ago
src	directory re-organization (keeps the old build system)	14 years ago
.gitignore	directory re-organization (keeps the old build system)	14 years ago
COPYING	directory re-organization (keeps the old build system)	14 years ago
README	directory re-organization (keeps the old build system)	14 years ago
README.md	Updated development process description	14 years ago

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the development forums: http://www.bitcoin.org/smf/index.php?board=6.0 The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.

Feature branches are created when there are major new features being worked on by several people.