The Veles Masternode project operates an open contributor model where anyone is welcome to contribute towards development in the form of peer review, testing and patches. The codebase is maintained using the "contributor workflow" where everyone without exception contributes patch proposals using "pull requests". This facilitates social contribution, easy testing and peer review.
Development of Veles Masternode follows the same guidelines does the Veles Core, hence this document should be understood as an extension of the document Contributing to Veles Core, which explains the practical process and guidelines for contributing.
Parts of the document Contributing to Veles Core** that are too project-specific are over-ruled by their Veles Masternode equivalents listed below.
... The title of the pull request should be prefixed by the component or area that the pull request affects. Valid areas are:
service
for changes to service definitions or proccess controlconfig
for changes to the configuration filesvpn
for changes related to the VPN / dVPN servicehttpd
for changes to the HTTP daemon excluding API changesapi
for changes to the masternode JSON API
Valid are also all the areas listed in the original document. Those are (if not stated otherwise in the latest version of document):
consensus
for changes to consensus critical codedoc
for changes to the documentationqt
orgui
for changes to veles-qtlog
for changes to log messagesmining
for changes to the mining codenet
orp2p
for changes to the peer-to-peer network coderefactor
for structural changes that do not change behaviorrpc
,rest
orzmq
for changes to the RPC, REST or ZMQ APIsscript
for changes to the scripts and toolstest
for changes to the Veles unit tests or QA testsutil
orlib
for changes to the utils or librarieswallet
for changes to the wallet codebuild
for changes to the GNU Autotools, reproducible builds or CI codemn
for changes to the masternode or governance code
By contributing to this repository, you agree to license your work under the GNU/GPL license unless specified otherwise at the top of the file itself. Any work contributed where you are not the original author must contain its license header with the original author(s) and source.