thanks

If you use Node.js, then you can run `npx thanks` to see which of your dependencies are seeking financial support. Demo GIF: https://github.com/feross/thanks/blob/master/img/example.gif GitHub repo: https://github.com/feross/thanks P.S. I am accepting donations here: https://feross.org/thanks/

There is thanks https://github.com/feross/thanks - with an open issue to read the URL from package.json https://github.com/feross/thanks/issues/2

I think the biggest chunk of people directly benefiting from OSS are companies, for whom Patreon might be an inefficient intermediary. Personally, I'd prefer my employer funnel a few thousand dollars to the the FSF, Python Software Foundation, etc. than setup a Patreon donation for each project we use. (Maybe some big ones like Redis and nginx and BackboneJS should get direct donations, but now many npm packages do we use? Oh god, so many.) That said, if you maintain an OSS tool, please do set up an easy way to donate. When it's easy to donate a dollar or two, I do (well...occasionally). I've found very few developers have Patreon's setup. Some will have a PayPal link, which is especially nice for random online tools that I use once or twice. Most don't provide an easy opportunity to contribute financially. Though I guess I should keep mo

Somewhat similar: https://github.com/feross/thanks

There's an NPM package started for this: https://github.com/feross/thanks

I've been rolling an idea around my head to interview and write up stories on some of these people. Here are some that fit (or come close to fitting) your description that I've been talking to: - https://sindresorhus.com - https://github.com/slact - https://www.patreon.com/microhq - https://github.com/feross/thanks/blob/master/index.js

So, that's my fault. To get things started, I added a bunch of authors who had accounts on Patreon and Librepay so `thanks` wouldn't start out completely empty. Specifically, I used the "Find My Friends" feature and just used the list that came up. (Paul had a LibrePay account receiving $0/month.) So, in the specific case of Paul it might not make sense to suggest donating to him for a Google project. Though, to be fair, he has a lot of packages on npm, some of which appear to be his own work (https://www.npmjs.com/~paulirish), so suggesting that you donate to him for time he's put into his own packages outside of work is fine in my book. The broader question is: how should we determine who to donate to? We could have packages declare explicitly if they're seeking donations and, if so, who to donate to. There's a proposal to do this here:

Interesting idea. What do you envision such a partnership would look like? Here's how I think about this. OpenCollective solves the problem of accepting payments and allocating those payments to maintainers in a transparent way (Patreon does this too, to some extent). `thanks`, on the other hand, just lets you know that a maintainer is asking for donations and directs you to their donation page which may be on OpenCollective. For example, these ones are: https://github.com/feross/thanks/blob/c203cc0248fe339e9ea4b8... I suppose `thanks` could do more, e.g. accept payments directly from the command line, or ask how much you're willing to donate and then suggest an allocation to each maintainer/team. But I wanted the v1 of this product to be super simple. It merely raises awareness that you may have dependencies looking for donations, but do