-
Notifications
You must be signed in to change notification settings - Fork 15
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
Express sustainability (funding deep dive) #228
Comments
I see a lot of potential in this initiative OpenJS foundation - New Ecosystem Sustainability Program (CPC approval is pending). Quick summary
|
I have two questions:
|
If there's an OC, then GitHub Sponsors can be hooked up to point to it. |
Just wanted to flag this comment here: expressjs/express#6064 (comment) I am a 👍 to this, but I think before we publish this we probably need just a bit more clear consensus visibly shown in the PR, since this is the first time we will directly message this to end users. Like the page is super bare bones, and I am not sure we want folks seeing it like that. I dont really know if it matters, but just wanted to flag it. |
Would love feedback on whether https://github.com/collective-funds/guidelines would be suitable for adoption for you. We announced our adoption on the Mochajs Open Collective earlier this year: https://opencollective.com/mochajs/updates/adopting-collective-funds-guidelines-0-1 |
As discussed in our last meetings, we agreed to do a deep dive session about this topic.
There have been several discussions (online, offline, public/private....) over the years and recently. The idea of this issue is to prepare the discussion for a deep dive session in the near future.
Historical context
Resources
Ideas to discuss on the session
The idea is to drop ideas/concerns/whatever is relevant to have enough context for the deep dive session.
Note: I will update this message frequently to act as an index for the session, as I can imagine that this thread will be quite long to read. As well, I make an effort to moderate it and keep it on track. Actually, any TC member can update it, so feel free to do it :)
The text was updated successfully, but these errors were encountered: