d4kmor

I assume you are referring to hacktoberfest. We did get a few good contributions from that but yeah it's dangerous if any contribution counts.

This got me thinking so I think those issues will need to be very well define - probably even with failing tests if possible. Also it's probably good to keep the number of bounty issues low for maintainability.

Seems there is still much to learn.

Interesting - I didn't knew that one. It seems very security related - I'm not sure if issues for not supporting a specific part in a spec or for improving documentation for a feature will fit in.

What do you think?

That sounds good. Needs to be very specific and easy to "check". I assume making such well defined bounty issues will require quite some work. If it's worth it only time will tell.

> I also would let the bounties be set by users rather than centrally.

So you mean go to an issue and say I will add another 50 bucks if that get's resolved. Makes sense and will certainly would require a system.

Having a dedicated HR found sound good we have been wondering how to call/do this.

Thanks for sharing your experience - it certainly helped staying realistic. It seems it will not magically lead to all issues being resolved by others. It was a slim hope but yeah probably more a dream then anything . It still seems worth a try