Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js should have an OpenCollective #919

Closed
ovflowd opened this issue Sep 10, 2024 · 3 comments
Closed

Node.js should have an OpenCollective #919

ovflowd opened this issue Sep 10, 2024 · 3 comments

Comments

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

Numerous projects on the JavaScript (and non-JavaScript ecosystem) and even under the Foundation (namely Jest, ESLint, and WebPack) have OpenCollective funding that allows the project to prioritize resources and reward long-standing collaborators for working on specific feature requests, security incidents, and bug fixes and dedicate spiking/research time to proposals and new features.

I bet that this was already suggested before, but recently, with my work on defining a governance model for Webpack (https://github.com/webpack/webpack-governance), it became clear to me that we should have an OpenCollective.

More importantly, we should have a model to allocate and disburse and a government amendment to support such endeavors.

With an OpenCollective, we can gather funds from individual contributors and enterprises, allowing us to spend more CI resources efficiently and pay for core collaborator's time (and any eligible Working group work).

From the bottom of my heart, please implement an OpenCollective and funding/disbursing model. We need this.

@ovflowd
Copy link
Member Author

ovflowd commented Sep 10, 2024

cc @nodejs/tsc

@aduh95
Copy link
Contributor

aduh95 commented Sep 10, 2024

Duplicate of nodejs/TSC#1553?

@ovflowd
Copy link
Member Author

ovflowd commented Sep 10, 2024

Duplicate of nodejs/TSC#1553

@ovflowd ovflowd marked this as a duplicate of nodejs/TSC#1553 Sep 10, 2024
@ovflowd ovflowd closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants