Skip to content

Milestones

List view

  • Support remaining governance action types as per CIP-1694 (Hard Fork Initiation, Update committee and/or threshold and/or terms, Protocol Parameter Changes)

    Overdue by 7 month(s)
    β€’
    Due by June 2, 2025
    β€’0/3 issues closed
  • As Governance moves forward we need to refine the support for each part of the process. The current focus in creating a Cardano Budget requires specific off-chain discussion and input from DReps.

    Overdue by 8 month(s)
    β€’
    Due by May 6, 2025
    β€’83/97 issues closed
  • ## 1. Decoupling Set up backend architecture to support the migration, requiring a separate backend repo. Frontend migration through a wrapper repo for smoother design integration. ## 2. New design system Migrating the application to a new design system sourced from the Figma atomic library and the respective GovTool theme. ## 3. Development Deploy backend updates, similar to the approach used for PDF management, with the backends serving as modular components. ## 4. Releases & Deployment Establish separate environments or feature flags for staged releases to minimize disruptions during the transition. ## 5. Testing Implement a dedicated test environment; adapt existing tests for new backend compatibility. Use specific containers for migrated components to ensure integrity and reduce regression risks. ## 6. Community Backlog Adjust GitHub structure to define a clear repo for community issue reporting and refine Usersnap configurations for enhanced feedback handling. ## 7. GitHub Actions Introduce automated actions for deployment, such as packaging and pushing updates to npm and creating boilerplate templates. ## 8. Multilanguage Support Ensure each repo includes its respective localization files to enable comprehensive multilingual support. ## 9. GitHub Views and Project Adjustments Adjust GitHub views and configurations across related projects, requiring significant operational updates. ## 10. UX Impact Monitor user experience for any disruptions or breaks, with risk mitigation strategies in place. ## 11. Communication and Marketing Develop a communication plan to inform and engage users through workshops or other events. ## 12. Documentation and Guides Update documentation, simplify user guides, and create tutorial videos, with support from the Open Source Committee and marketing.

    No due date
    β€’1/2 issues closed
  • This milestone contains tasks and issues for changes to GovTool to evolve after Plomin hard fork. This tickets SHOULD be completed after mainnet enters full governance.

    No due date
    β€’35/74 issues closed