pull down to refresh
654 sats \ 3 replies \ @dk 4 Mar \ on: Draft of SN Open Source Contribution Award Rules meta
I love how you're being thoughtful about how to align incentives here, @k00b. I don't have specific opinions about changes to suggest, but I wonder how much of this is adopting existing best practices from other open source bounty programs, how much represents innovation in incentive systems, and how to judge success of this proposal.
If this breaks new ground in FOSS incentives and succeeds it could help positively influence other projects.
Thanks!
I wonder how much of this is adopting existing best practices from other open source bounty programs
I haven't looked at other open source bounty programs so any similarity would be a coincidence and/or I'm just huffing from the same can of zeitgeist. I made 50% of this up over the last month then last 50% yesterday. But it's all based on my experience over the last year or so which was pretty informative.
how much represents innovation in incentive systems
Probably not much. Some of this is new to paid FOSS work I'd guess, but incentive systems are pretty simple as I see them. Pay for good. Punish for bad. Try to make sure good and bad are well defined and verifiable and where they aren't assume an oracle or collections of them (and make sure they're paid).
and how to judge success of this proposal.
Anything that gets more people contributing meaningfully would be a success imho. FOSS just incentivizes contributions that poorly by default. Beyond that, I'd like to get enough contributions to iterate on the incentive structure/rules and get some more full time hires.