No description, website, or topics provided.
Clone or download
Pull request Compare This branch is 12 commits ahead, 36 commits behind JohnDolittle:master.
Permalink
Failed to load latest commit information.
contrib start Dec 9, 2015
doc start Dec 9, 2015
share start Dec 9, 2015
src should probably go to sleep ;\ Aug 25, 2016
.gitattributes Build identification strings Apr 10, 2012
.gitignore start Dec 9, 2015
COPYING start Dec 9, 2015
INSTALL start Dec 9, 2015
README directory re-organization (keeps the old build system) Apr 23, 2011
README.md start Dec 9, 2015
swagbucks-qt.pro bump version Apr 4, 2016

README.md

SwagBucks development tree

SwagBucks 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 SwagBucks.

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'.