Crowdfund reverse-bounties for open-source issues
First, run the development server:
yarn devOpen http://localhost:3000 with your browser to see the result.
- Email notifications for bounty status changes
- Prevent donations on closed issues
- Test batch refunder
- Test issue checker
- Maybe make Stripe webhook into Trigger job
- Convert staging to prod and make another staging instance
- Consider switching to app router and dropping tRPC
- Email notifications for bounty status changes
- Multi-currency support for global contributions
- User profiles for tracking contributions and refunds
- Social sharing options to promote bounties
- Automated bounty release approval based on paying donor approval
Stripe fees could become costly for small payments where we expect lots of refunds. We need to be careful about how we handle this.
- Stripe charges a fee for payments ~(2.9% + 30c)
- Stripe may charge a fee for refunds
- https://support.stripe.com/questions/understanding-fees-for-refunded-payments
One option to solve this is a Gofundme-style "tip" option, where the donor can choose to cover the fees. This might be the best option for now, with a checkbox that says "I am happy to cover the fees for this payment, of around ~$0.36".
Another solution would be to take a cut of the bounty awarded to the developer and hope that this covers the fee costs in aggregate. There is a risk that the number of failed bounties greatly exceeds the number of successful bounties, and we end up losing money.
There might be a way to charge people later - i.e. the "payment" is more like an agreement to pay when the bounty is claimed. This would be a bit more complex and harder to launch with, but it could be a longer term solution.