Kleros
Kleros.ioGithub
  • Introduction to Kleros
  • Kleros FAQ
  • Governance
  • PNK Token
  • They talk about Kleros
  • Products
    • Court
      • Kleros Juror Tutorial
      • Famous Kleros Cases
      • What happens during a dispute?
      • Kleros & Credible Neutrality
    • Court V2
    • Proof of Humanity
      • Proof of Humanity 2.0 Tutorial: (Register & Vouch)
      • Proof of Humanity 2.0 Tutorial (Remove & Challenge)
      • Proof of Humanity 2.0 Tutorial (Transferring a Profile)
      • Proof of Humanity 2.0 Integration Guide
      • Proof of Humanity FAQ
        • Proof of Humanity 2.0 launch FAQ
    • Curate
      • Kleros Curate Tutorial
      • Kleros Scout
        • Tutorial
        • Earn With Kleros Scout
        • Partnerships
        • Kleros Scout - Metamask Snaps
          • Knowledge Base
        • FAQs
    • Oracle
    • Governor
    • Escrow
      • Kleros Escrow Tutorial
      • Kleros Escrow Specifications
    • Linguo
      • Kleros Linguo Tutorial
      • Step-by-step Tutorial
        • Requesting translations
        • Working as a translator
        • Reviewing translations
      • F.A.Q
      • High-level Overview
    • Moderate
      • Susie
        • Getting Started
          • Add Susie
          • Start Susie
        • Basics
          • Welcome
          • Language
          • Notifications
        • Rules
        • Reports
        • Evidence
        • Federations
  • INTEGRATIONS
    • Overview
    • Industry use cases
    • Types of Integrations
      • 1. Dispute resolution integration plan
        • Smart contract integration with Kleros Court (Arbitrator)
        • Use Cases
          • DeFi Insurance
          • Gaming
          • Recognition of Jurisdiction Integration
            • Integración por Reconocimiento de Jurisdicción
        • Channel partners
          • How to use Reality.eth + Kleros as an oracle
          • Safe Zodiac integration
          • Kleros Reality Module
        • Integration Tools
          • Centralized Arbitrator
          • Dispute Resolver
      • 2. Curated-data integration plan
        • Retrieving information from Kleros Dapps
    • Policy writing guide
    • Live & Upcoming Integrations
    • Kleros Analytics
    • Scalability & Cross-chain
      • Using Kleros arbitration for Dapps on xDai/Gnosis
    • Integrations FAQ
  • Developers
    • Arbitration Development
      • ERC-792: Arbitration Standard
      • ERC 1497: Evidence Standard
      • Arbitrable Proxy
    • Arbitration by Example
      • ArbitrableDeposit.sol
      • TwoPartyArbitrable.sol
      • Rental.sol
      • ArbitrableTransaction.sol
      • MultipleArbitrableTransaction.sol
      • MultipleArbitrableTokenTransaction.sol
    • Deployment Addresses
    • Curate Classic: Integration for Devs
    • Light Curate: Integration for Devs
    • Guide for Preparing Transactions
  • Contribution Guidelines
    • Overview
    • General Dev. Workflow
      • Task Tracking & Lifecycle
      • Releases
    • Smart Contract Workflow
      • Task Tracking & Lifecycle
      • RAB - Review, Audit, Bounty
      • RABd (+ Deploy)
      • Reporting Vulnerabilities
    • Code Style and Guidelines
      • Git
      • Solidity
      • Web Languages
    • License & Code of Conduct
      • License
      • Code of Conduct
  • Additional Resources
    • Discord
    • Telegram
    • Governance Forum
    • Twitter
    • Blog
    • Reddit
    • Github
    • Slack
Powered by GitBook
On this page
  • All in Github
  • Labels for Days
  • Optional
  • Priority
  • Status
  • Type
  • Lifecycle

Was this helpful?

Edit on GitHub
  1. Contribution Guidelines
  2. General Dev. Workflow

Task Tracking & Lifecycle

Our methodology for keeping track of development work.

PreviousGeneral Dev. WorkflowNextReleases

Last updated 2 years ago

Was this helpful?

All in Github

See for our message and branch names style and guidelines.

We try to keep the number of tools we use to a minimum for simplicity and ease of onboarding. The new features of Github make it possible to keep most of the project management next to the code, and this is our approach:

Issues
Projects
Milestones

Reference a specific task and keep track of its status.

Reference a long term project or goal.

Are used to group issues into time-controlled sprints.

Labels for Days

We also have a very comprehensive set of labels that can be automatically added to a repo using . It's important that all issues and pull requests have a priority, status, and type, and that they keep track of who is working and who is reviewing, if anyone.

Optional

  • duplicate 2️⃣ - Is a duplicate.

  • starter 🍼 - Good for new contributors.

Priority

  • Critical 🔥 - Mission critical.

  • High - Top of to-do list.

  • Low - Bottom of to-do list.

  • Medium - Somewhere in the middle of to-do list.

Status

  • Abandoned - The assigned contributor gave up.

  • Available - Open for anyone to work on.

  • Blocked - Blocked by another issue.

  • In Progress - Someone is already working on it.

  • On Hold - Purposely paused.

  • Proposal - Don't work on it until accepted.

  • Review Needed - Pending reviews.

Type

  • Bug 🐛 - Bugs.

  • Documentation 📚 - Documentation work.

  • Enhancement ✨ - Enhancements.

  • Maintenance 🚧 - Chores.

  • Question ❔ - Queries about the project.

Lifecycle

The lifecycle of a task goes like this:

We don't have a complicated issue or pull request template, we just ask for common sense and for all necessary information.

  1. An issue is raised with the description of what needs to be done.

  2. Discussion takes place and someone is assigned to the issue.

  3. The issue is added to a project and/or milestone, if applicable.

  4. The assignee branches off develop to work and submits a pull request when ready.

  5. Our CI/CD process lints, formats, and tests the code.

  6. The pull request is merged after all the changes are reviewed and accepted, and any requested changes are made.

Git Code Style & Guidelines
Kathari