# Roadmap for Open Source Projects

> See how open source maintainers use Featul as a public roadmap and feature voting board separate from GitHub Issues.

Canonical: https://www.featul.com/use-cases/open-source-roadmap

Open Source. Open source maintainers drown in GitHub Issues that mix bugs, questions, and feature wishes. Featul gives the community a voting board and a public roadmap without turning every +1 comment into another issue.

## The challenge

Common friction points this use case is built to solve.

### GitHub Issues get cluttered with feature requests

Feature requests in Issues compete with crash reports, so maintainers triage noise instead of direction.

### Hard to gauge community interest vs noisy minority

A vocal minority comments daily while quiet users who actually ship patches never vote.

### Roadmap visibility limited to contributors

People who are not contributors cannot see what is planned unless they live in the repo.

## How Featul helps

A clearer workflow from feedback intake to shipped updates.

### Dedicated feature voting board separate from Issues

A dedicated voting board sits beside GitHub so Issues can stay focused on bugs and PRs.

### Public roadmap for community alignment

Unique votes and a bias check show whether demand is broad or just a few loud accounts.

### Clear contribution guidelines integration

A public roadmap explains Planned, In Progress, and Shipped without promising dates the project cannot keep.

## Frequently asked questions

### Is Featul an open source product feedback tool?

Featul itself is MIT-licensed and self-hostable, and this use case is built for maintainers who want a public roadmap without turning GitHub Issues into a voting app.

### Can the community vote without a GitHub account?

Yes. Share a public board. Visitors can browse and vote without cloning the repo or opening an issue they will never see again.

### How is this different from a Featurebase alternative for OSS?

You get the same board-plus-roadmap loop, with the option to self-host. That matters when the project cannot put community data on a closed vendor.

## Related

- [Feature Voting Bias Checker](https://www.featul.com/tools/categories/feedback-roadmaps/feature-voting-bias-calculator)
- [Slack Integration](https://www.featul.com/integrations/slack)
- [Featurebase alternatives](https://www.featul.com/alternatives/featurebase)
- [Compare with Alternatives](https://www.featul.com/alternatives)
- [View all use cases](https://www.featul.com/use-cases)
