7 ms·
Pay successful bounty submissions on a faster than net 180 time frame. A friend was interested in the rather extensive Expensify bug bounty programme [0], but t
by jpt4 2y ago
Pay successful bounty submissions on a faster than net 180 time frame. A friend was interested in the rather extensive Expensify bug bounty programme [0], but the red tape involved created far too long a turnaround time between claiming a ticket and receiving compensation.
[0] https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22 https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aiss...
- Suppafly 2y agoDo they get to claim it and then work on it, or do they need to have a solution already to claim it? net 180 wouldn't be bad if you could reserve several of them to work on at a time. It'd suck to work 'for free' that first few months, but then you'd have consistent income coming in regularly after that.
- MiscCompFacts 2y agoI think I would prefer whomever fixed the bug first, I know that’s not ideal for people who put the time and effort in.
- Suppafly 2y agoI guess it depends if you're the one doing the paying or the one receiving the pay .