-
Notifications
You must be signed in to change notification settings - Fork 138
Don’t use bountysource anymore! #547
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
Comments
Ouh, that's bad. Unfortunately, I also wasn't even aware of the "inactivity fee", so I lost all my money I earned. Damn. @jospoortvliet Please deactivate the bountysource integration for this repository. |
@jospoortvliet is on vacation for the next two weeks as far as i know. There are a few issues in this repository which have bounties on them. Maybe you should post something there @korelstar ? |
Since the new Terms of Service were withdrawn, I think we have won some time. I will wait for @jospoortvliet 's comeback then, since this is his part and his bot is still active. Maybe he can organize the complete removal of bountysource, including the text "Want to back this issue? ..." and link to bountysource that was added by his bot to every issue. |
ping @jospoortvliet: please deactivate the BountySource integration and remove BountySource links from all issues. |
I saw this pinned Issue before contributing to a bounty, but I didn't click through to it, and I subsequently forgot about it. Should someone maybe go through and edit the P.S. I deleted my off-topic comments on the other Issue (which I'm deliberately not pinging), so you can delete your response there, too, if you'd like. (I can edit out this paragraph from this comment shortly.) |
I don't know. The bountysource integration was done by @jospoortvliet and I asked him to remove it but I got no answer 😞 I really don't like the current situation, but I can't speak for the Nextcloud organization, which is responsible for this stuff. Maybe they can give an official advise. |
Seems to be disabled as far as I can tell. |
Uh oh!
There was an error while loading. Please reload this page.
Bountysource decided to update their Terms of service today:
Also check the discussion at: https://help.nextcloud.com/t/stay-away-from-bountysource/84943
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: