Add `funding` fields to packages about collective HOT 6 CLOSED

I'd suggest updating the top ~25-50 packages as a start. I'd imagine there's quite a long tail of packages with less downloads. 🤷‍♂

from collective.

Could this field be automatically added the collective using github-tools or npm-tools?

from collective.

GH tools can’t push to repos or publish packages (the latter step is needed for funding to take effect.) Automatically publishing packages can also be dangerous because they may contain unreleased non-patch changes.

Node’s package maintenance project (which concerns itself with the ecosystem better), also recently added a new support field in package.json. It’s an interesting proposal, and for unified I drafted this example to try it out (it defines me as potential paid/contracting support option):

"support": {
  "versions": [
    {
      "version": "^7.0.0", // (current major?)
      "target": {
        "node": "active"
      },
      "response": [
        {
          "type": "regular-7", // 7 days unpaid response time for free by volunteers
          "paid": false,
          "contact": {
            "name": "Volunteers",
            "url": "https://github.com/unifiedjs"
          }
        },
        {
          "type": "24-7", // 6 hours paid response time (could also do `regular-1`)
          "paid": true,
          "contact": [
            "Titus Wormer <[email protected]> (https://wooorm.com)"
          ]
        }
      ],
      "backing": {
        "sponsored": "https://opencollective.com/unifiedjs",
        "paid-support": "https://wooorm.com"
      }
    }
  ]
}

from collective.

GH tools can’t push to repos or publish packages (the latter step is needed for funding to take effect.) Automatically publishing packages can also be dangerous because they may contain unreleased non-patch changes.

But it could add the field across hundreds of repos, so it will be there when the next release is cut.

from collective.

Yes, true! But there’s no code for changing Git repo’s yet, so that would take a significant amount of time. I image the work to do that is also a lot, because we have monorepos as well, and package.json files in test suites. So it’ll be hard to automate.
I estimate the manual work to be 24-32 hours, which has the benefit of walking through every repo, updating deps, fixing some issues, etc. Automating will cost at least 16 hours?

from collective.

The highly starred and highly downloaded packages have funding fields now!

[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
├── type: opencollective
├── url: https://opencollective.com/unified
├─┬ [email protected]
│ └── url: https://github.com/sponsors/isaacs
└─┬ [email protected]
  └── url: https://github.com/sponsors/ljharb

from collective.