No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib first commit Aug 11, 2017
doc first commit Aug 11, 2017
release first commit Aug 11, 2017
share first commit Aug 11, 2017
src fixy stuff Aug 15, 2017
.gitattributes first commit Aug 11, 2017
.gitignore first commit Aug 11, 2017
.qmake.stash first commit Aug 11, 2017
COPYING first commit Aug 11, 2017
INSTALL first commit Aug 11, 2017
PlayerCoin-qt.pro fixy stuff Aug 15, 2017
README first commit Aug 11, 2017
README.md first commit Aug 11, 2017
compile-blk.sh first commit Aug 11, 2017

README.md

PlayerCoin development tree

PlayerCoin is a PoS-based cryptocurrency.

Development process

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

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, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of PlayerCoin.

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

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. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.