nodejs / nodejs/TSC

Self-serve model for funding Node.js work

Open
#1,747 30 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
694
Forks
142
PR merge metrics
No merged PRs in 30d

Description

@nodejs/tsc I'm sharing this concrete proposal to further address any concerns regarding https://github.com/nodejs/TSC/issues/1723#issuecomment-2827713134 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:

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the discussion in TSC issue 1723, the proposed nodejs.org header change, and Nodejs-Funding-Sources.md. Then inspect the nodejs/admin repository location proposed for the maintainer directory. Done means the funding page, discoverable navigation link, and directory approach are agreed and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
content, documentation, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.