Hacker News Reader

Comment by C1sc0cat | Hacker News Reader

$300 just buys you a half day of developer time, I suspect the sponsor wants a proper professional job done that works with and is tested with a range of hardware.

View on HN

On my own open-source projects, there are hundreds or thousands of issues I'd solve in half a day if I got $300/ea. That'd keep me fully employed for months or years! And I actually have the users that would donate 6 figures / year cumulatively to make that a reality. But orchestrating the money would be a nightmare without a service that is simple to use from the users' perspective. BountySource is alright, but I'm not impressed. It's still a bit difficult to use and navigate compared to the average checkout system, or Kickstarter itself.

Kickstarter is more suitable for larger projects.Github could work with a little bit creativity on top, however that's the place for technical people. A platform,where a feature could be requested and payouts are as simple as one click would be fantastic. I think the platform part would be the easiest to implement.To ensure the whole thing works well for devs and clients well+ doesn't attract bad actors,etc. would be more difficult to get right.

With 300 for a half-day, it would be 600 for a full day and 12000 for 20 days of work.

In most parts of the world, that's an extremely high level salary and could easily fund most peoples month, granted they live outside of Silicon Valley.

I'm sure many people would be more than happy to receive 300 or much less for half a day of work.

$300 is gross. You have to pay taxes on this. In many developed countries this would be $150 after taxes.

Can we stop talking about $300? It was a random number used as a variable that can be replaced with any dollar amount.

The going rate for a developer is about £300-600 a day in North Europe for relatively common skillsets such as C#. It isn't just silicon valley.

The $10,000 bounty is about right for this sort of work. In fact it might be a little low, but I have no idea how OBS works internally so I could be completely wrong.

I don't think it's a problem of OBS, but the problem of writing a dummy v4l-device it seems. which IS more complicated! (though I wonder what it's used for)

But my point was its not a quick half day fix for some minor formatting on a website - which you can out source offshore.

Your talking windows audio /video internals which is not a common skill

I believe the goal included linux also.

Reply on news.ycombinator.com