Would joining the OpenJS Foundation be worth considering?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, node.js, postgresql
Research direction
The issue names no files, tests, or code entry points. Start by reviewing the proposal with the project maintainers and any existing discussion about OpenJS Foundation membership; done means reaching a documented decision on whether to pursue incubation or close the proposal.
Written by the indexing model from the issue text.
Description
While contributing to node-postgres, I started wondering whether joining the OpenJS Foundation might be worth considering for the project’s long-term future.
node-postgres has become critical infrastructure for a large part of the Node.js ecosystem, but much of its maintenance and responsibility still appears to fall on you. A neutral foundation could potentially help reduce that burden over time by providing a structure for broader governance, involving more maintainers, improving continuity, and offering support around security, infrastructure, legal matters, and project sustainability.
I realize that this would involve a real trade-off. Moving toward open governance would mean sharing some of the control and decision-making authority you have built and maintained over the years. The onboarding process would also create some additional work initially, and joining a foundation would not magically provide new maintainers. However, it could create better conditions for distributing responsibilities and reducing the project’s dependency on a single person in the longer term.
Given node-postgres’s maturity, adoption, and importance to the Node.js ecosystem, it seems like a strong potential fit for OpenJS, probably starting through its incubation process.
I do not know whether this has already been considered or discussed privately, and of course this is ultimately a decision for you and the project’s maintainers. I just wanted to raise the idea and see what you think.
- Dominant language
- JavaScript
- Stars
- 13.2k
- Forks
- 1.4k
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from brianc/node-postgres
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
brianc/node-postgres#3770 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
brianc/node-postgres#3716 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
brianc/node-postgres#3631 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
brianc/node-postgres#2857 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
brianc/node-postgres#2433 ·
All issues in brianc/node-postgres
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100