Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
danielroe
approved these changes
Jan 30, 2026
garthdw
approved these changes
Jan 31, 2026
Member
|
do you think it's worth a separate npmx-dev/governance repo so when we make changes the git history is easy to follow? |
Contributor
Author
|
I prefer we keep this document in the main repo for now. Later on we could move to a separate governance repo when there are more repos in the org and the complexity is big enough |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ALT:
danielroe — Yesterday at 21:41
hello everyone! 👋
... and apologies for the ping, but now seems a good time to talk about what npmx is as an open source project.
it was 8 days ago that I made the first commit, and I had something I was excited about a day later. it was clear to me from the community that it would be big, and I invited patak to join two days later.
it's impossible to believe that it's been less than a week since we started inviting close allies and trusted folk. we're already at 75+ npmx contributors, and around 200 people on the server now, which is an outstanding percentage.
so now seems like a good time to make explicit what 'npmx' is:
we're open-source and for the good of the web
we're a community project, built by all of us
it might be a bit early for it, but patak and I have drafted a governance doc to set out a bit about how we want to steward npmx. it's short but we'll be filling it out more as we go on.
we've also created an opencollective so we can help support the community and hopefully, one day, help other similar projects.
we want to make the experience of using npmjs better for us and for others. and the joy of open source is that we can do that together! I hope it goes without saying, but thank you ❤️
we'd love your thoughts on the document and on the project 🙏
patak — Yesterday at 21:41
I also want to say sincerly thanks to y'all! This has been such a beautiful week. I still can't believe how much we have been able to build together. From my side, I believe this project is going to be a force of good for the ecosystem, so I plan to dedicate considerable time to work on it. Here for future shared adventures! Cheers to you and to the future of npmx ❤️