Labels

• A-easy

  Relatively easy change, good first issues
• A-important

  High-impact, important change
• A-needs-research

  Information is needed to proceed. Remove this label when the information gets filled in.
• B-broken

  Existing content is broken (code bugs, wrong information)
• B-missing

  Missing documentation
• E-examples

  Examples in the form of code snippets or word problems
• I-client

  Documentation specific to Iroha clients
• I-concepts

  Core Iroha concepts (data model, operations, mechanics)
• I-peer

  Documentation specific to Iroha peers
• L-application

  Integrating Iroha into external environments
• L-config

  Configuration, customization
• L-metrics

  Collecting data about the state of Iroha
• L-setup

  First steps (installing, building, etc.)
• L-troubleshooting

  Handling when something does not work as expected
• L-versioning

  Issues relating to versioning
• M-dependencies

  Pull requests that update a dependency file
• M-epic

  Issues/PRs that depend on other items (e.g. tracking issues)
• M-meta

  Issues/PRs on the documentation itself (presentation, localization, navigation, etc.)
• M-QA

  Quality assurance on the documentation
• must-be-done
• S-guide
• S-reference
• T-cli

  CLI documentation
• T-javascript

  JavaScript-related documentation
• T-jvm

  Java/Kotlin-related documentation
• T-python

  Python-related documentation
• T-rust

  Rust-related documentation
• zh-migration