Comment on A new way to support open-source: OpenPledge

Thekingoflorda@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

• zigxBenx@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

  Open Collective also supports open-source projects, but Open Pledge has a more granular, results-based approach. With GitHub API integration, Open Pledge can automatically detect merged pull requests, which enables funds to be distributed based on specific contributions rather than general funding. This system encourages and rewards ongoing, measurable contributions, making it easier for pledgers to see direct results and for contributors to receive fair compensation tied to their work.

  source

  • yetAnotherUser@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago

    So it’s like a bounty system then? Wouldn’t that contribute to low-quality PRs that are rushed to get the money ASAP? And what if the company tries to cancel the bounty right before the commit is pushed, when all the work is done?

    source

    • zigxBenx@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

      Yes, that’s a great point! After extensive discussions with both maintainers and companies interested in Open Pledge, we found an optimal solution: the maintainer or project owner connects their project to Open Pledge and flags specific issues as eligible for pledging. This way, contributors know which tasks are open for funding. Once a donation is made, it cannot be canceled, providing stability and commitment to the contributor—unless it has an expiration date, which is clearly displayed upfront for transparency.

      I hope that makes sense :)

      However if you see any other possible issues please let me know!

      source

      • yetAnotherUser@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago

        OK, sounds good to me. Thanks for the quick reply.

        source
  • Thekingoflorda@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Ah, very nice!

    source