Skip to content

cutepuppydog5/garbagecoin

 
 

Repository files navigation

Garbagecoin Core integration/staging tree

Build Status

Garbagecoin is an awesome digital currency that enables instant payments to anyone, anywhere in the world. Garbagecoin uses technology to operate with no central authority: managing transactions and issuing money are carried out collectively by this thing. Garbagecoin Core is the name of open source software which enables the use of this currency.

For more information, see https://sites.google.com/view/garbagecoin/home.

License

Garbagecoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of Litecoin Core.

The https://github.com/garbagecoin-project/ does not exist The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #garbagecoin-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Please buy I want it to go to the moon pls buy

Translations

We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to Garbagecoin periodically.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Releases

No releases published

Packages

No packages published

Languages

  • C++ 62.1%
  • Python 15.9%
  • C 11.2%
  • Assembly 6.3%
  • M4 1.6%
  • Shell 1.1%
  • Other 1.8%