[PINNED] - Guidelines for submitting and voting on issues.

[bitbound]

Community voting and feedback is essential for helping me to determine the priority for features and bugs. Without votes, I'd have no way of knowing which features are wanted most by the community, or which bugs are appearing most frequently.

To help with this, I've adopted a simple voting system using GitHub reactions. Here's how it works:

Voting on Issues

• Each issue (bug report or feature request) will be weighted by total number of 👍 (thumbs up), total number of 👎 (thumbs down), and the total sponsorship level for the user accounts associated with the reactions.
• To vote for an issue, add a 👍 reaction to the issue.
• To vote against an issue, add a 👎 reaction to the issue.
  • For example, you can vote against a feature request if you think it shouldn't be implemented, or if you think it should be implemented differently.
  • If you think it should be implemented differently, you're encouraged to leave a comment to suggest an alternative approach.
• If another user has suggested an alternate implementation in a comment, you can also add a 👍 or 👎 reaction to that comment to indicate your agreement or disagreement with their suggestion.

Employer/Vendor Sponsors

• If your vendor or employer is sponsoring ControlR, please mention that in the issue so I can add it to my internal weighting calculations.

Feedback Requests

• The feedback_requested label indicates that I'm seeking feedback from the community on a particular topic.
  • The issue list can be filtered to show only these items.
• If you have feedback on the topic, please leave a comment.
• Feel free to use 👍 or 👎 reactions on the comment to indicate your agreement or disagreement with the feedback provided.

Roadmap

• You can view the project board here: ControlR
• The board will only contain issues that are planned, being worked on, or completed.
• I haven't committed to a public roadmap yet with concrete timelines, but I might in the future.
  • Since I'm still "finding my footing", I don't want to over-promise and under-deliver at this stage.

Submitting Issues

When submitting a new issue, please use the issue templates and provide as much detail as possible.

For bug reports, please remember that if I can't replicate the issue, it's unlikely I'll be able to fix it or write tests to prevent regressions.

Why are votes weighted by sponsorship level?

ControlR is now my sole source of income. As such, I need to prioritize features and bug fixes that will have the most impact for sponsors and will keep the project financially sustainable.