Skip to content
Hawkkit Core
C++ C Python CSS M4 Makefile Other
Branch: master
Clone or download
Latest commit 50552c8 Nov 11, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Initial commit Nov 10, 2019
.tx Initial commit Nov 10, 2019
build-aux/m4 Initial commit Nov 10, 2019
ci Initial commit Nov 10, 2019
contrib Initial commit Nov 10, 2019
depends Initial commit Nov 10, 2019
doc Initial commit Nov 10, 2019
docker Initial commit Nov 10, 2019
qa Initial commit Nov 10, 2019
share Initial commit Nov 10, 2019
src Initial commit Nov 10, 2019
.gitattributes Initial commit Nov 10, 2019
.gitignore Initial commit Nov 10, 2019
.travis.yml Initial commit Nov 10, 2019
CMakeLists.txt Initial commit Nov 10, 2019
CONTRIBUTING.md Initial commit Nov 10, 2019
COPYING Initial commit Nov 10, 2019
INSTALL.md Initial commit Nov 10, 2019
Jenkinsfile
Jenkinsfile.gitian Initial commit Nov 10, 2019
Makefile.am
README.md Initial commit Nov 10, 2019
autogen.sh Initial commit Nov 10, 2019
configure.ac Initial commit Nov 10, 2019
libhawkkitconsensus.pc.in Initial commit Nov 10, 2019

README.md

GitHub Logo

Hawkkit Hub Core v1.0.0.0-g (HTU)

https://www.hawkkit.com

What is Hawkkit?

Hawkkit (HTU) is the best investment system app which will help you showcase your business, lifestyle, social, or shopping app in the best possible manner.

License

Hawkkit 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Hawkkit Core.

The contribution workflow is described in CONTRIBUTING.md.

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.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

You can’t perform that action at this time.