remotion

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

Hey HN! We’re Ioannis & Zaf, building Algora.io to help open source projects reward their contributors & grow their communities. 1 min demo: https://twitter.com/algoraio/status/1641560954746839042 The problem: paid contributions in open source are scarce, low trust & high friction Our solution: we built an app that streamlines open source bounties on Github Our 1st customer was Remotion.dev (15.6k stars, Typescript/React) in November 2022, whose feedback helped us ship our Github app & iterate through our bounty workflow. To date, Remotion.dev has rewarded 17 open source bounties: https://github.com/remotion-dev/remotion/issues?q=label%3A%2... Since then, we’ve been fortunate to also onboard Cal.com (17.6k stars, Typescript/Next), IHP (3.9k stars, Haskell), Qdrant.tech (5.4k stars, Rust), erxes.io (2.8k stars, Typescript) and shuttle.rs (