-
Notifications
You must be signed in to change notification settings - Fork 0
NPM maintainers? #18
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
Comments
Of course it may be possible for someone else with repo access to just publish a new version, but I'm not 100% sure. |
|
Repo access is not enough. You do have to be made an I have started working on some modules to help us with these type of issues. When we have something more formalized, I will be sure to share. |
Cool. Then just go with the flow if I just go ahead and add someone. 😄 I'm at a point in life where I'm really sick of wasting time on ill-fated projects of one sort or another. |
Added @Planeshifter + @mikolalysenko to a bunch of stuff. Nothing personal, @kgryte! Don't hesitate to ask if you want to contributing to anything for which I have permissions. Just a redundancy check until a better solution is found. |
+1 :) |
Yeah, I need to be more diligent about this, but it is hard to stay on top of with the npm interface. I think @hughsk had a script which automated some of this? Anyway as a temporary measure I'll start adding some maintainers manually. |
https://github.com/repo-utils/npm-org-rights does wonders :) |
Oh, important to note that you need iojs or |
Awesome, thanks! Yeah, just trying hard to push some of this tedious organizational stuff forward. I'll see if I can set that up. |
Ok! It is done. I added all you guys to scijs using npm-org-rights. You all should do the same! |
The syntax for that command is:
|
Is it necessary or even possible to establish some sort of npm organization in order to prevent orphaned modules? I see this: https://docs.npmjs.com/cli/owner but that sounds like we'd have to manually add a couple maintainers for every module, which would be a pain unless done programatically. Just trying to figure out how to avoid a bad situation.
The text was updated successfully, but these errors were encountered: