IntersectMBO / IntersectMBO/govtool

Thank you, and what’s next for GovTool

Open
#4,216 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
21
Forks
29
Avg merge
2d 22h
Merged PRs (30d)
7

Description

Hi all,

First, a thank you to everyone who has contributed to GovTool in any capacity — writing code, reviewing it, filing bugs, testing releases, arguing about the UX, or simply telling us when something was broken. GovTool is what it is because of you.

Sireto Team (@mesudip, @kussal, @sireto-sandip) is onboarding as new maintainers taking over the day-to-day operational ownership of GovTool. Here is what we would like to do next:

- *Clean up the issue backlog.* A lot of what is open is outdated or already resolved. We will go through it and close what no longer applies, so the remaining issues actually reflect the work to be done.
- *Bring all GovTool components into one repository.* Parts of GovTool currently live outside this repo, which makes the project harder to follow and harder to contribute to than it should be.
- *Make running GovTool locally easier.* Standing up the full stack should be a short, documented path, not a research project.
- *Lean less on self-hosted Cardano infrastructure.* Running GovTool today means running a Cardano node and a cardano-db-sync instance, which is a heavy burden for a contributor and a large operational surface for us. Where mature community-run projects and providers already solve this well, we would rather build on them and work with those teams than duplicate the effort.
- *Make contributing easier.* Clearer setup, clearer docs, and faster review.
- *Replace the Haskell backend with TypeScript.* This lowers the barrier to entry considerably and lets far more people work across the whole codebase.
- *Integrate better with other community projects.* There is a lot of good work happening across the Cardano governance space. GovTool should connect with it rather than sit apart from it, and we want to talk to the teams building it.
- *Publish a governance digest.* A regular, subscribable summary of what is actually happening in Cardano governance — active governance actions, votes, outcomes — so people can follow along without having to watch the chain themselves.
- *Make GovTool the best open source governance tool on Cardano* — and keep it open.

We would like to do this with the community rather than in front of it. If you have opinions on any of the above, especially the backend rewrite, we would rather hear them now. Issues and pull requests are open, and we are happy to talk through anything before it is decided.

Thank you.
Sireto team

Contributor guide

Open the contributing guide

Research direction

This issue is a maintainer announcement and does not name files, tests, or a concrete entry point. Start by reviewing the proposed backend rewrite and repository/setup changes, then split the roadmap into focused issues with explicit completion criteria; this issue itself has no single definition of done.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell, typescript
Domain
backend, documentation
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.