Sabbaticals
nayafia opened this issue · 5 comments
I'm inspired by the GSOC model of funding student developers to work on open source projects.
The part I think they get right is A) making it a dedicated, focused period of time vs. ad-hoc "whenever I get around to it", and B) providing stipends to make it financially feasible.
The part I think could be iterated upon is A) providing stipends to experienced contributors, not just students, and B) widening the scope of projects to include more niche stuff. And, obviously, C) making it a year-round thing.
What do you think about providing paid "sabbaticals" for contributors to work on an open source project for a dedicated 1-3 months, a la GSOC? It would be harder for those with full-time jobs, I think, but people might be able to knock out a lot instead of dragging their to-dos out with a couple hours/wk here and there.
This would be nice, but as you said - it isn't really feasible for those working full time, nor is it feasible for those that can't fund it. This really boils down to a "where does the cashflow come from" question, I think.
Yeah, where the $ comes from (and how much there is available) really sets the parameters of what's feasible. I think companies are a good place to start. Stripe started an experiment last year called the Open-Source Retreat where they provided $20K grants for 2-4 contributors to work on their projects for 3 months.
I think sabbaticals could work for maintenance as well, not just new features. Hard part is having to fit the work into cycles: say, 3 months of paid time to knock out the big to-dos, enough to sustain another 9 months of ad hoc work.
This model has also been adopted by http://outreachy.org/ to steady success. The funding comes from donations from companies interested in funding diversity outreach.