Add infrastructure support to Ecosystem funds

[andrew]

Along side most used packages within an ecosystem, it would be great to also be able to donate to the various infrastructural pieces that support those packages and the ecosystem.

Things like:

• package manager clients
• package manager registries
• runtimes and programming languages
• foundations and governance
• build tools
• community infrastructure like forums, CI, git hosting

Discovering these things won't be quite as automatic as with packages but perhaps can be easy to contribute if we had a yaml file for each ecosystem in a repository that people can send pull requests to.

Also need to work out what share of allocations should go to the extra infra, probably some default percentage that can be customized per fund.

Notes:

• some foundations cover lots of the individual pieces, others don't
• only open source infra will be eligable, for instance npmjs.com the registry is not open source

[sethmlarson]

Thanks for opening this issue @andrew! This definitely represents more work than the automated aspects of package dependencies, but I think it'll be worthwhile especially considering how the funds are grouped. Volunteering to do the research for you for Python:

• CPython (reference implementation for the Python programming language) uses GitHub Sponsors.
• pip (Most common package manager for Python, bundled w/ CPython and other implementations), along with many important projects under the PyPA (setuptools, twine, virtualenv) uses GitHub Sponsors
• PyPI (Warehouse) is run by the Python Software Foundation, which also uses GitHub Sponsors.