Feedback Boards for Open Source Maintainers
Open source maintainers can use Request Mark as a simple feature voting layer while keeping issue trackers focused on bugs and implementation details.
When it helps
Why teams use this
Scattered feedback slows small teams down
startups, indie hackers, SaaS teams, and micro-SaaS builders often hear requests across email, support, calls, chat, and founder replies. Request Mark gives that signal a structured place to live.
Internal tools are not public feedback tools
Delivery tools are useful after a decision is made. A feedback board helps users submit, vote, and follow requests before work becomes an internal ticket.
Visible progress builds trust
Statuses and admin updates help users understand whether a request is new, planned, in progress, shipped, or closed.
What this helps you do
After setup
What improves after setup
A clearer intake path
Teams get one page to share when a customer asks for a feature, instead of manually copying notes into a spreadsheet or backlog.
Better prioritization signals
Votes, comments, requester identity, and status history create a more useful demand picture than memory or gut feel.
A faster path to delivery
When a request has enough signal, the team can move it into Linear, Trello, or the delivery system that owns implementation.
How it works
- 1Create a board for the project or package.
- 2Link it from docs, README files, or community spaces.
- 3Review top-voted requests before planning releases.
- 4Close the loop with shipped updates.
FAQ
Can Request Mark replace an issue tracker?+
No. It is better used as a feature request and voting layer before work becomes an implementation issue.