Skip to content

Don’t use bountysource anymore! #547

Description

@stefan-niedermann

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.

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.

Activity

  1. locked as resolved and limited conversation to collaborators on Jun 17, 2020
  2. korelstar commented on Jun 17, 2020

    @korelstar
    Member

    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.

  3. stefan-niedermann commented on Jun 17, 2020

    @stefan-niedermann
    MemberAuthor

    @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 ?

  4. korelstar commented on Jun 19, 2020

    @korelstar
    Member

    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.

  5. korelstar commented on Aug 22, 2020

    @korelstar
    Member

    ping @jospoortvliet: please deactivate the BountySource integration and remove BountySource links from all issues.

  6. elsiehupp commented on Mar 14, 2021

    @elsiehupp
    Member

    @stefan-niedermann Please read the pinned issue "Don’t use bountysource anymore! ". @korelstar maybe you should remove the bounty sums from the issue titles.

    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.)

  7. korelstar commented on Mar 14, 2021

    @korelstar
    Member

    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.

  8. juliusknorr commented on Jan 3, 2023

    @juliusknorr
    Member

    Seems to be disabled as far as I can tell.

  9. unpinned this issue on May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions