-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rysolv isn't working #3084
Comments
Thanks for opening this. I labeled it as a discussion. We had few criteria when were choosing the platform:
Now, if you and other members of the community have any suggestions about the platform, please list them here and also specify how much do each of these suggestions match our criteria. We are not exclusive with Rysolv, we can have our bounties on other platforms (with the only criteria that for each ticket only one bounty platform should be used). |
@mmahmoudian I've looked at Rysolv's page for Flameshot and there's been only ONE issue created for Flameshot in 2 years (until today when I've added another one). Moreover, that issue was created by yourself.
It's clear that Rysolv has had no external usage, and has produced zero results in two years. Why do you think that is?
Some hypotheses:
Too small userbase. Rysolv is 20 times less popular than Bountysource. I see you contacted Bountysource in 2021 and they didn't reply. What did they have to reply with? Bountysource already lets anyone create a bounty, and is far more popular than Rysolve. Gitpay is another popular bounty service. There are bounty hunters on Bountysource who've made tens of thousands. Rysolv doesn't have anything like that.
The advice to post on Rysolv hasn't been as clear as it could've been. For example
#4
at Fails when fractional scaling <> 100% #564 (comment) could've linked directly to an issue.What do you think? What are the pros and cons of Rysolv vs. the much more active Bountysource? Which bounty tracker would benefit the health of the Flameshot project more?
The text was updated successfully, but these errors were encountered: