pull down to refresh
I just paused them. As is, they are biased toward producing code and that's the easy part now.
Somehow, we need to gate/award folks based on specification, QA, and code review.
I suspect having:
- a higher reward for detailed issues
- a grave penalty, like 50% for a single requested change
- banning future contributions when something is totally off base
might be enough
reply
Have you thought about requiring an upfront payment for a PR to be considered? Which would be refunded when it's successfully merged?
Losing 50% for a requested change would probably turn me off from even trying, honestly. That’s a big hit. But I recognize the challenge here
reply
it's still on the
README.md, so maybe they didn't take it away. I vaguely recall @k00b mentioning stopping it because of too many bots. But my recollection may be faulty.