Permalink
Switch branches/tags
0.9.3 7_change_wallet 15-private-blockchain 18-monigoring-token-transactions 22-money-transfer-1000-optimization 24-console-setup 26-block-collection-boosting 56-desync-monitoring 70-smart-refactoring 109-vde-notifications-fixed-import 172-autoupdate-notification 200-rewrite-rollback 203-block-transaction-timeout 220-db-cache-batch 221-get-query-cost-formula 283-add-rollbacks-hash-to-block 289-edit-contract-bug 316-no-sqlite-tests 365-playblock-bugfix 409-console-setup 432_contract_deactivation 447-this_host 750-daemonparser-refactoring 1000_node_E_UPDATING_timeout 1079_running_mode 1081_vde_params_removing 1257-new-ecosystem-param AP-29-no-getAllTables Moving_api_to_models add_menu_and_page_for_new_vde_front centrifugo changing_of_initial_parameters cmdline_reset del_old_functional develop_without_config develop double-database feature/fix-vdecontracts-error feature/vde-contracts feature/384-blockchain-relevance-alternative feature/447-work-with-VDE-from-applications feature/466-add-VDEMode-support feature/481-block-generation-time feature/506_syslog_logging feature/518-updater-changes feature/572-login-changes feature/594-net-id feature/636-application-table-fixes feature/637-basicapp-tables feature/648-lang-appid feature/662-fullnodes-json feature/678-login-salt feature/701-login-api feature/709-rollback-fix feature/738-node-owner-condition feature/739-testify feature/746-centrifugo-scheme feature/748-multitx feature/752-api-refactoring-2 feature/759-fuelrate-cost feature/762-members-wrong-count feature/764-no-updatelang feature/788-calculate-moneydigits feature/793-calculate-change feature/830-calculate-fix feature/864-contracts feature/866-delayed-contracts feature/885-network-protocols feature/892-ecosystem-tables-error feature/893-admin-app feature/907-request-cache feature/930-content-disposition feature/948-blockchain-leveldb feature/950-metainformation-storage-refactoring feature/957-sys-params feature/962-desync-monitor feature/972-lang-scope feature/988-wrong-default-page feature/1001-fullnodes feature/1024-table-permissions feature/1034-sim-files feature/1037-newsql feature/1039-fix-duplicated-tx feature/1040-date-time feature/1067-send-tx feature/1079-running-mode feature/1087_contracts_with_confirmation feature/1097_remove_UUID_func feature/1107-fixed-login feature/1110-get-history feature/1132-increase-attempt-count-db-lock feature/1142-vm feature/1182-parameters-rename feature/1197-vde-restore feature/1199-body-size feature/1213-app-id feature/1214-maxbody-config feature/1216-dublicate-tx feature/1219-history feature/1233-api-blockid-changed feature/1242-span feature/1246-func-bench feature/1253-wallet feature/1254 feature/1256-hexpub feature/1258-app-content-api feature/1260-update feature/1262_remove-ecosystem-variable feature/1263-dbfind feature/1264-data feature/1265-cors feature/1266-params feature/1268-parse feature/1269-sections-api-update feature/1272-block feature/1275-appcontent-api-fixed feature/1279-network feature/1280-menu-changed fixing_blockchain_errors fixing_queue_blocks full_nodes_from_syspars gorm_converters_refact gorm_open_host hofix/966 hotfix/1.0.1 hotfix/1.0.2 hotfix/1.0.4 hotfix/1.0.5 hotfix/1.0.6 hotfix/966 hotfix/1040-data-time hotfix/1059-version hotfix/1236-history-hash hotfix/1260-update hotfix/1261-addresstoid-error hotfix/1268-parse hotfix/1272-block hotfix/1274-keyinfo hotfix/1280-menu-changed install_without_restart local_1000tx logs_with_from_function looped_transactions master_logging master menu_and_page_for_new_front merge_two_bastards money-transfer-commented-opt no_upd_full_nodes origin/develop private_key_in_file process_bad_tx_fix refactoring release/0.9.1 release/1.0.0 release/1.1.0 revert-237-578-getUID-returns-vde-status revert-601-feature/752-api-refactoring-2 rp-822-problem statsd_monitoring supported_old_chain upd_readme3
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
93 lines (69 sloc) 4.11 KB

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
  3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is SemVer.
  4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@apla.space. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4