BigBang Network Official Development Repo

Website : BigBang Website

Wiki: BigBang Wiki

Whitepaper: BigBang Whitepaper(中文)

Whitepaper: BigBang Whitepaper(EN)

Repo Guidelines

• Developers work in their own forks, 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 development team members simply pulls it.
• If it is a more complicated or potentially controversial change, then the change may be discussed in the pull request.
• 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 the coding guides) or are controversial.
• From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.