Enhancement (Meta): Create processes to pull sponsorship data

[JacobCoffee]

Summary

We need to be able to pull sponsor data from our various sources.

This will include sources from:

• GitHub Sponsors (GraphQL API)
• OpenCollective
• Polar.sh

Preferably this is an automated process done on each release so that documentation can be automatically updated to reduce maintenance burden.

This would also be useful for release notes, but we still need to automate that a little better (❓)

APIs Available

• Polar.sh API
• OpenCollective API
• GitHub Sponsors GraphQL API
  • https://docs.github.com/en/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account is also a thing

Basic Example

No response

Drawbacks and Impact

No response

Unresolved questions

• Is this service managed by GitHub Actions or an external process (which we could run periodically via GitHub Actions or keep up to receive webhook events mentioned above?)
• I would like to list individual sponsors as well as the larger ones, so we should pull everything we have.

---

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

• If you would like to see an issue prioritized, make a pledge towards it!
• We receive the pledge once the issue is completed & verified
• This, along with engagement in the community, helps us know which features are a priority to our users.

[provinzkraut]

Is this service managed by GitHub Actions or an external process

How about we collect set up a GH Action that periodically runs (e.g. once a day), fetches the data and pushes the updates to GH pages? We could put a JSON file somewhere in there that the docs then load in and display a list of sponsors, that way we won't need to do a full doc rebuild.

[JacobCoffee]

😲 i like it

this is why you're paid the big bucks