You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bountysource decided to update their Terms of service today:
2.13 Bounty Time-Out.
If no Solution is accepted within two years after a Bounty is posted, then the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. For Bounties posted before June 30, 2018, the Backer may redeploy their Bounty to a new Issue by contacting [email protected] before July 1, 2020. If the Backer does not redeploy their Bounty by the deadline, the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource.
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.
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 <bountysource-plugin> section in each Issue to explain the situation? I mean, I have write access to do so myself, but I don't want to step on your toes here... @korelstar suggested removing the sections entirely, but it does seem useful to leave up references to the bounties that still exist.
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 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.
Activity
korelstar commentedon Jun 17, 2020
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.
stefan-niedermann commentedon Jun 17, 2020
@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 ?
korelstar commentedon Jun 19, 2020
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.
korelstar commentedon Aug 22, 2020
ping @jospoortvliet: please deactivate the BountySource integration and remove BountySource links from all issues.
elsiehupp commentedon Mar 14, 2021
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
<bountysource-plugin>section in each Issue to explain the situation? I mean, I have write access to do so myself, but I don't want to step on your toes here... @korelstar suggested removing the sections entirely, but it does seem useful to leave up references to the bounties that still exist.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.)
korelstar commentedon Mar 14, 2021
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.
juliusknorr commentedon Jan 3, 2023
Seems to be disabled as far as I can tell.