Live data from Hacker News

Ask HN: Patreon for open source?

news.ycombinator.com

11–20 of 63 posts

Re: Ask HN: Patreon for open source?

#12

Paying per commit seems as sensible as paying per LOC (related story: [1]). Simple recurrent monthly donations as one can easily set up (eg. on Flattr) make more sense, in my opinion. [1] http://www.folklore.org/StoryView.py?story=Negative_2000_Lin...

Patreon has a feature to limit the number of payments per month for "per creation" campaigns.

It's good for keeping track of exactly how much you'll be spending.

Anecdote: 3 of the 10 campaigns I've "pledged" to use per creation, the rest are monthly.

Re: Ask HN: Patreon for open source?

#13
What I'd really like to see is some sort of business account for Patreon or one of the others. Lots of companies use open source projects as an integral part of their day-to-day work, yet it does not seem straightforward to set up a monthly contribution to this work for a company. Obviously, they can use one-time grants to the Apache Software Foundation or someone else, but sometimes it is really just a single developer or a couple of developers that develop a crucial software package (webpack and others). Would be great if a company could support this easily as well.

Re: Ask HN: Patreon for open source?

#14
> $X for every commit

Even if you're supposedly giving money to reputable developers that are the percentile less likely to commit fraud, there's still a risk of it happening.

A more reasonable approach would be a monthly or a "version" contribution.

Even better than that would be a "fund" where you pledged your money to developers/projects, and it would be distributed equally or by a clear metric.

Re: Ask HN: Patreon for open source?

#15
There is [Gratipay](https://gratipay.com/~Gittip/) which is based on donations. You might look into that as well. A commit I think is not representing anything apart from the fact that it is a (hopefully) compound piece of code. You might want to pay for finished user stories which are estimated properly.

Re: Ask HN: Patreon for open source?

#17

Paying per commit seems as sensible as paying per LOC (related story: [1]). Simple recurrent monthly donations as one can easily set up (eg. on Flattr) make more sense, in my opinion. [1] http://www.folklore.org/StoryView.py?story=Negative_2000_Lin...

Yup, that makes sense. Do you have an idea for a better indicator of development activity we can tie into? I thought about telling the contributor how many commits the team makes on an average month, and capping the maximum contribution they'd like to make.

Re: Ask HN: Patreon for open source?

#19
"Give some love to open source devs."

It turns out that many users of open source projects (especially libraries and packages) are other developers !

It is hard to find a piece of modern software which doesn't depend on some open source libraries. Those libraries might depend on other libraries and so on. Just do an `npm ls --depth=4` in a node-based project to see what a nice tree that is. Same thing with cocoapods, carthage, rubygems, pip, cargo, leiningen, etc.

In my view, money should follow the project structure - developers should donate part of the money they receive to the project dependencies and the devs of the dependencies should do the same thing, recursively and that's how you really spread the love !

I've started working on a prototype a year ago, but got discouraged after someone showed me that there are literally hundreds of projects trying to 'spread the love' and as a consequence no love is being spread :)... so I kind of gave up on it for now, but still think this is how it should be done.

Re: Ask HN: Patreon for open source?

#20

Exists: https://whispersystems.org/blog/bithub/ Snowdrift looks interesting too: https://snowdrift.coop/

I am not sure about Snowdrift. Although the project has an interesting take on crowd funding, it has been in development since late 2013 and does not seem to be making any significant progress. As far as I can tell, it is still in alpha stage and without a working payments system.
Post reply on HN