This is interesting and I genuinely hope you succeed because OSS funding is important.
I have some questions:
1. Can anybody place a bounty on any issue? That seems like it could take control away from the maintainer. Is there a way for a maintainer to reject an issue bounty, so they can keep control over the direction/architectural decisions of the project?
2. Could someone pledge money towards a milestone (e.g. the next major version) rather than specific issues?
3. Are you offering any kind of business support to maintainers, such as reaching out to business users on their behalf to negotiate a sponsorship/support contract/bounty/etc? The sales part of all of this seems like it's the biggest challenge for OSS projects where it's just a few engineers who don't have the time or skill to do sales.
Fantastic questions & feedback – thank you @bogwog!
1. Yes they can, but they remain anonymous and private only for the maintainer to see and take action on. Currently, we don't have automation for explicit rejection/approval, but something we want to add. Completely agree re: maintainer control – it's a core principle of ours.
I have some questions:
1. Can anybody place a bounty on any issue? That seems like it could take control away from the maintainer. Is there a way for a maintainer to reject an issue bounty, so they can keep control over the direction/architectural decisions of the project?
2. Could someone pledge money towards a milestone (e.g. the next major version) rather than specific issues?
3. Are you offering any kind of business support to maintainers, such as reaching out to business users on their behalf to negotiate a sponsorship/support contract/bounty/etc? The sales part of all of this seems like it's the biggest challenge for OSS projects where it's just a few engineers who don't have the time or skill to do sales.