Read URL from package.json

[egoist]

Feel free to close it if this tool is only made for the maintainers and projects listed in https://github.com/feross/thanks/blob/master/index.js

The feature request is to support "thanks": "url" field in package.json so that all packages with this field set can be displayed in the thanks table. 😄

[feross]

This is a neat idea.

[hackergrrl]

Decentralize! ❤️

[zkat]

One thing worth noting is that you can already add arbitrary contact info for individual authors, which might also be preferable. See the expanded contact info I use for my projects, which already integrates with weallbehave for figuring out who to contact. You can probably reuse this field easily enough, or use it for lookup.

[egoist]

Yep something like author.donation author.patreon author.openCollective look good to me too 😄

[qubyte]

Using the expanded author info is intriguing, particularly when using the url field. If that URL served a document with a link or anchor tag for donations, this'd work well with indie web:

https://indieweb.org/payment
http://microformats.org/wiki/rel-payment

[marijnh]

This'd also address the problem of the burden of keeping the donation link data accurate being on you (if this takes off, I can imagine people submitting PRs to associates some popular developer with a patreon they control)

[tunnckoCore]

I'm both for thanks field and inside author. 🎉 🌮

[btkostner]

The url field is designed to be a homepage link, which may or may not be a donation link, but it would be best to keep them seperate. While the thanks field would work for this project, I personally think we should use the donation field. It's general enough that it can be used in other projects, and hopefully eventually be a part of the package.json spec. Secondly, allowing contributors.donation has the added benifit of being able to have multiple donation links for a package.

Down the line if we need more information, the donation field could be expanded to an object, similar to the repository field.

{
  "donation": {
    "type": "patreon",
    "url": "..."
  }
}

[pubkey]

if we put the donation-data inside of a .thanks.json, this logic can later be reused with non-npm-projects.

[qubyte]

@btkostner To be clear, my suggestion does not change that url is for a homepage. The rel-payment microformat (see links) is a way of discovering a donation URL within a page (either as a link tag or an anchor tag). This means that anyone/anything visiting a homepage with one will easily be able to discover a way to donate.

[qubyte]

(something explicit in the package file would also be good, but this would be nice to have as another mode of donation discovery)

[adrianheine]

I would love to see @qubyte's suggestion implemented, both for ideological reasons and to ease maintenance. This should only work over HTTPS and validate certs, though. Also, explicit info from package.json should have precedence.

[qubyte]

@adrianheine Agreed on all counts. I'm putting a module together now which does this. I may make the suggestion as a separate issue so I don't hijack this comment thread any further.