3 ms·

Maybe an internal voting system, where every SWE gets 1 vote, but they submit a couples projects (as a fallback mechanism), so at the end of the yr all donation

by dmix 4y ago

Maybe an internal voting system, where every SWE gets 1 vote, but they submit a couples projects (as a fallback mechanism), so at the end of the yr all donations get bunched up & paid out together. Then if the money can't go to the first project for whatever legal reason it goes down to the next one of their list. It's still a complicated system so it'd would take serious buy in. Not to mention the drama donations generate internally and publicly. But it's a noble goal. $1000 per engineer grant might still be easier and less fragile

SethMLarson 4y ago
This is part of what Spotify did to determine urllib3 as an award recipient: https://engineering.atspotify.com/2022/04/announcing-the-spotify-foss-fund/ https://engineering.atspotify.com/2022/04/announcing-the-spo...
sandyarmstrong 4y ago
This is what Microsoft does, basically. Each month, $10,000 is donated to some project. Anyone who has contributed to any open source repo during that month is eligible to vote. There's a good nomination system, too. The write-ups for each candidate are done by employees.
- dmix 4y ago
  I still like OPs idea of it being more 1-to-1, where the engineer votes their $1000 on a specific project and that's the project that gets it. It's not just a ranked voting mechanism where a top few get it. The system would only be there to bunch up "votes" so if multiple people choose one project it gets paid out in one bulk payment w/ a fallback to other projects if that payment fails.
  - sandyarmstrong 4y ago
    Yeah, I'd be prefer that as well. But I understand why it might be harder to accomplish.
- CydeWeys 4y ago
  $10,000/month for a company the size of Microsoft is so little, though. And only one award per month is way too few as well. I still like my idea of $1,000/yr/engineer of allocations, with monthly batching on the rewards. Also you'd be able to see which projects are already getting substantial support, and then maybe use that information to reward your smaller dependencies that aren't getting as much attention.

by dmix 4y ago

SethMLarson 4y ago

This is part of what Spotify did to determine urllib3 as an award recipient: https://engineering.atspotify.com/2022/04/announcing-the-spotify-foss-fund/ https://engineering.atspotify.com/2022/04/announcing-the-spo...

sandyarmstrong 4y ago

This is what Microsoft does, basically. Each month, $10,000 is donated to some project. Anyone who has contributed to any open source repo during that month is eligible to vote. There's a good nomination system, too. The write-ups for each candidate are done by employees.

dmix 4y ago
I still like OPs idea of it being more 1-to-1, where the engineer votes their $1000 on a specific project and that's the project that gets it. It's not just a ranked voting mechanism where a top few get it. The system would only be there to bunch up "votes" so if multiple people choose one project it gets paid out in one bulk payment w/ a fallback to other projects if that payment fails.
- sandyarmstrong 4y ago
  Yeah, I'd be prefer that as well. But I understand why it might be harder to accomplish.
CydeWeys 4y ago
$10,000/month for a company the size of Microsoft is so little, though. And only one award per month is way too few as well. I still like my idea of $1,000/yr/engineer of allocations, with monthly batching on the rewards. Also you'd be able to see which projects are already getting substantial support, and then maybe use that information to reward your smaller dependencies that aren't getting as much attention.