Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

thank you for your input! the best way to ensure everyone has a great experience is to spec & scope bounty issues + provide acceptance criteria.

you can look at Remotion's 17 completed bounties, where specs & acceptance criteria are always included: https://github.com/remotion-dev/remotion/issues?q=label%3A%2...

that being said, we have only had a handful of projects using OSS bounties so far so we haven't seen everything under the sun. I acknowledge what you mean by blurry lines and how/when they might occur. but as I said before, when specs/scope/acceptance-criteria are in place, it's really hard to go wrong



Defining as acceptance criterion "must fit my style" is just not concrete enough..


where did you see that? not sure what you're referring to




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: