Self-serve model for funding Node.js work

[RaisinTen]

@nodejs/tsc I'm sharing this concrete proposal to further address any concerns regarding #1723 (comment) before moving forward with implementation.

Problem statement

Companies and individuals want to fund Node.js work. Some Node.js maintainers are open to receiving funding for their contributions. How can we provide a self-serve way for funders to connect with those maintainers?

My proposal

Host a directory of maintainers and their areas of interest and expertise in an easily discoverable place on the Node.js website.

Add a new "Funding" item to the headers list in https://nodejs.org. It would be a link to a new page with contents:

Funding Node.js

This page outlines how you can fund the project and its maintainers.

1. Directed funding for OpenJS Foundation Member

Organizations can become OpenJS Foundation Members and use directed funding to support the project. To learn more about Project Directed Funding, visit https://openjsf.org/projects.

2. Donate via GitHub or Open Collective

The project accepts funding via:

• GitHub
• Open Collective

Funds are to be used for specific efforts as decided by the Node.js Technical Steering Committee, including:

• Security lead
• CI stability improvements
• Project health and collaboration

For more details, see Node.js Funding Sources.

3. Fund individual contributors

The following directory lists maintainers who are open to receiving funding:

(Link to a file in https://github.com/nodejs/admin which would contain this directory)

Name	Contact	Areas of interest and expertise
Jane Doe	jane.doe@gmail.com	Modules, Website
John Doe	john.doe@gmail.com	HTTP, Async hooks

Companies and individuals may connect directly with maintainers. The Node.js project does not oversee these engagements and is not responsible for any disputes or outcomes.

[avivkeller]

FYI @nodejs/nodejs-website

[mcollina]

As a nonprofit organization, I don't think this is viable as is with our current policies and programs and it needs a few tweaks:

1. Being an OpenJS Foundation member and use directed funding to support the project https://github.com/openjs-foundation/cross-project-council/blob/main/project-resources/project-directed-funding-policy.md
2. Donate (not sponsor) via GitHub or OpenCollective
3. Fund individual contributors, without listing anyone but pointing to https://github.com/nodejs/node/blob/main/README.md#collaborators, which already has the "support me" link there. We should not mention that they are availble for sponsored work.

Note that the board has not forgotten about this and we will be implementing a partner program for companies to be listed as implementation partners.

[RaisinTen]

I've updated it to address points 1 and 2.

Regarding point 3, not listing anyone but pointing to the collaborators list has some limitations that might make it less effective for funders and maintainers:

• It lacks info about areas of interest and expertise of maintainers, which is important for funders who want to support contributions in specific areas.
• It doesn't include maintainers outside the collaborators list, such as those working on the website, which is a critical part of the project.
• Not everyone listed there is open to receiving funding or being contacted for this.
• From a reader's perspective, browsing a section of the GitHub README markdown file feels less accessible and discoverable than seeing this presented on the Node.js website.

That's why I thought a separate, opt-in directory, limited to those open to receiving funding and including info about their areas of interest and expertise, on the Node.js website makes more sense. Any thoughts?

[mcollina]

This was discussed in the TSC meeting and we agreed to include the list in the Admin repository.