3 ms·
I doubt it'll work out. Other than highly mechanical tasks, the time investment to resolve an issue is unpredictable. It's highly unlikely someone only interes
by trinovantes 6y ago
I doubt it'll work out.
Other than highly mechanical tasks, the time investment to resolve an issue is unpredictable. It's highly unlikely someone only interested in monetary compensation would just randomly pick up an issue in a random repo and work on it. There's a reason why most contractors bill by the hour rather than by number of JIRA tickets closed.
Even if there are people interested in the bounty, it'll eventually turn into the 99designs of coding: dozens of people competing to be the first to resolve an issue and that usually results in a drop in quality for speed (see Goodharts law)
- Rperry2174 6y agoYeah I guess I'm picturing it being more for "mechanical" tasks. For example, in our case we have a tag called "new profilers" (https://github.com/pyroscope-io/pyroscope/issues?q=is%3Aissue+is%3Aopen+label%3Anew-profilers https://github.com/pyroscope-io/pyroscope/issues?q=is%3Aissu...) Which TLDR is they are reporting agents for each respective language that send profiling data to our server. I'd picture the bounty as us just giving an input and an output in the form of a set of unit tests and just saying: "if you create a java agent that passes these tests we will pay you $X" Seems "mechanical" enough right?