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

doc: first cut at sponsor agreements, and sponsor page documentation #955

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

mhdawson
Copy link
Member

@mhdawson mhdawson commented Mar 5, 2025

No description provided.

jasnell
jasnell previously approved these changes Mar 5, 2025
@mhdawson
Copy link
Member Author

mhdawson commented Mar 5, 2025

@ovflowd I think this captures what we talked about today.

I think it captures an attempt at the process we'd need for the logos as well as what will go on the main nodejs.org landing page and the sponsor page without the logos.

I think it might be useful to add the sponsor page and links in the main landing page, even without sponsors (something like I have with the ? or this could be you. We can then fill it in as sponsors complete the required agreements.

@jasnell jasnell dismissed their stale review March 6, 2025 21:02

Actually, I need to review the background on this a bit more

Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Marking this as changes requested because I know I need to review this a bit more and I think there may be some conflicts in this approach with what the Foundation needs to do. Need to research a bit more

@mhdawson
Copy link
Member Author

mhdawson commented Mar 6, 2025

I should have mentioned that I've already looped in @bensternthal to suggest changes to bring the process into line with the experience from the foundation.

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a soft block here, as there are a few aspects of this I need to investigate with the board. I’ll get back with a longer explanation.

@mhdawson
Copy link
Member Author

mhdawson commented Mar 7, 2025

I was informed today that the project is not allowed to raise funding in this way based on this wording in https://openjsf.org/projects.

Project Funding Opportunities
All funding received through OpenJS Foundation membership dues is used to support various programs that benefit our hosted projects, and to run the Foundation. This funding is administered by the Board of Directors, which is comprised of elected community leaders and member company representatives.

The OpenJS Foundation recognizes that in addition to supporting the general activities of the OpenJS Foundation (through membership, event sponsorship, and certification), some organizations may wish to contribute additional monetary funding to the OpenJS Foundation for activities that benefit specific projects or initiatives.

OpenJS Foundation members who are current on their annual dues may contribute additional amounts of incremental monetary funding to specific OpenJS Foundation initiatives, such as roadshows, Cross Project Council activities, or project infrastructure. Directed monetary funding activities must be approved by the OpenJS Executive Director, and are subject to the following annual limits:

Platinum members: No cap on directed monetary funding
Gold members: Capped at 50% of annual dues amount
Silver members: Capped at 25% of annual dues amount

The Board of Directors may approve exceptions on a case-by-case basis.

Please note that these limits only apply to incremental monetary funding contributed directly to the OpenJS Foundation.  Aside from OpenJS Foundation membership and the incremental monetary funding described above, we strongly encourage organizations to invest in the health and sustainability of the community at large by employing contributors, encouraging and supporting employees as they grow into leadership roles, running local meetups, and open sourcing their projects.

I am surprised since I did my best to share the approach and goals along the way in the collaborator summit and in documentation Nodejs-Funding-Sources.md
and had thought that the help from the Foundation in setting up GitHub sponsors and Open Collective meant it was a reasonable direction but that was obviously not the case.

It sounds like the issue will be taken to the board for discussion on March 17th and we may get some alternate suggestions.

@ljharb
Copy link
Member

ljharb commented Mar 7, 2025

I'm confused; none of the quoted wording talks about anything except dues and directed contribution limits through the Foundation - is there a different clause that suggests that funding from non-member sources isn't allowed?

@mhdawson
Copy link
Member Author

mhdawson commented Mar 7, 2025

@ljharb no there is no other clause and it is the one I was quoted. I asked the same question but was told my interpretation was incorrect and that the clause applies in a way that prevents us from doing what's outlined.

@ljharb
Copy link
Member

ljharb commented Mar 7, 2025

That wording then is wildly insufficient (and either way, it's just a random page, it's not like a charter or TOS or anything) so if that's actually the case it needs better documentation.

@mcollina
Copy link
Member

mcollina commented Mar 9, 2025

I'm on this. I'll try to find some strategy that makes sense for the project.

I'm personally not aware of that direct funding ever be used, so maybe we can publicize that.

@ovflowd
Copy link
Member

ovflowd commented Mar 9, 2025

FYI that projects like Webpack and ESlint heavily depend on the ability of self funding to run and manage their operations -- including, somewhat, day to day maintenance.

@Balmasexy
Copy link

Marged together setup dashboard

mhdawson and others added 4 commits March 18, 2025 15:14
Co-authored-by: Antoine du Hamel <[email protected]>
Co-authored-by: Antoine du Hamel <[email protected]>
Co-authored-by: Antoine du Hamel <[email protected]>
Co-authored-by: Antoine du Hamel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants