Patreon

[babakness]

Have you guys considered setting up a Patreon account like Evan You / Vue.JS? I'd love to see RiotJS grow to be even more awesome, more efficient, faster, leaner, etc.

https://medium.com/the-vue-point/the-state-of-vue-1655e10a340a#.gi0fy3xxd

[cognitom]

Cool. But we already have the page on Pledgie.
https://pledgie.com/campaigns/31139

[GianlucaGuarini]

@babakness I am not sure Patreon is the right tool for riot.
Here a list of reasons:

1. Evan will work 100% on vue together with other collaborators being payed monthly thanks to the users offers and that's perfect for Evan (that I really admire as developer) however not all guys working on an open source project will need it.
2. Personally I don't feel "enough fool" to work 100% only on Riot and its ecosystem, I would like to have enough time and to explore and work also on other open source projects during my professional life...
3. I don't want to charge/ask monthly money to our users for something I do willingly whenever I have time
4. I don't need offers or money I need time, being an open source project maintainer and employed 100% at same time, means that time is the only limit I have at moment. Consider also that I have a social life/family/girlfriend/band and I can't get burned out working 24 a day just because users offer few money to let me stay like a monkey on a computer.
5. Riot will grow independently from the users offers, It will need probably more time but I recommend you to check also our releases frequency isn't one release almost every month enough?
6. Do less and do it good that's the only thing I wish at moment for riot, for all the rest there are million of npm modules that must play well with our framework because it tries to stick as closest possible to the standards. I had the chance to work only with vue during the last few months and as much as I love Evan's job I must admit that I feel sometimes it's too much: vue and it's ecosystem tries to provide everything (and nothing) you need to work on medium/big js applications but it contains a lot of "magic" and quirks that dragged me soon in the rabbit hole (some of them were clearly bugs Vue router and hot reload vuejs/vue-cli#129 $refs in loops are not in sync - the sub components instances do not get updated vuejs/vue#3204) - I hope I will have time for a detailed blog post about it

I hope my answer was enough and out of curiosity, @babakness how much have you offered in our already online Pledgie campaign?

[babakness]

@GianlucaGuarini $50 just now :-)

I'm a bit confused by the post. You guys DO take money, so why not open yourselves up to a re-occuring revenue model? I don't believe people pay because they expect you to give your soul to Riot, they just want to support your time--here on Github and when you're improve the framework. Easy enough. I'm personally more of a pay as I want guy but I know a lot of people want to offer ongoing support.

Think about it and thanks for Riot.

[rstacruz]

I'm a bit confused by the post. You guys DO take money, so why not open yourselves up to a re-occuring revenue model?

I'm not involved in Riot.js but I can answer this. (Note my answer might be different from @GianlucaGuarini's, but it's a general sentiment that should apply to most open source authors.)

---

I already have full-time work. I work 8-12 hours a day and get paid enough for it.

Doing open-source outside of my work is basically me giving away my free time because I want to do it. It'd be much like how an artist-on-the-side (with a day job) would paint—simply because she loves to paint.

Being paid an extra $30 a month isn't going to get her to commit to painting (or me to coding). Being paid for a commitment outside my work hours is also work. That's the definition of a job. Is it worth it? If I work 30 hours a month (eg, once a week) on the side for a project, isn't it as if I'm saying I'm worth $1/hour?

Maybe if you pay me for 30 hours on my hourly rate, then I'd consider. Maybe I can negotiate go to my dayjob 4 days out of 5, and work on open source on the extra day. But until then, my open source work will only fall into one of 2 categories: (1) done for the love of it, or (2) done as part of my dayjob *.

(<aside> * = the reason I'm able to contribute to open source is because it's tied to my work. I use open source tools at day job, so it's in my interest to write them and improve them. If I'm not writing things out of my own personal exploration, I'm likely writing things with an (in)direct correlation to my work.)

[GianlucaGuarini]

closed with #2239