Skip to content

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

Open
rreusser opened this issue May 11, 2015 · 12 comments
Open

NPM maintainers? #18

rreusser opened this issue May 11, 2015 · 12 comments

Comments

@rreusser
Copy link
Member

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.

@rreusser
Copy link
Member Author

Of course it may be possible for someone else with repo access to just publish a new version, but I'm not 100% sure.

@Planeshifter
Copy link
Member

npm owner add is not so bad. I do not think npm has organizations or anything like that (yet).

@kgryte
Copy link

kgryte commented May 11, 2015

Repo access is not enough. You do have to be made an owner of an NPM module. One way to automate the process is via git hooks or some other build process.

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.

@rreusser
Copy link
Member Author

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.

@rreusser
Copy link
Member Author

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.

@kgryte
Copy link

kgryte commented May 11, 2015

+1 :)

@mikolalysenko
Copy link
Member

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.

@hughsk
Copy link
Member

hughsk commented May 12, 2015

https://github.com/repo-utils/npm-org-rights does wonders :)

@hughsk
Copy link
Member

hughsk commented May 12, 2015

Oh, important to note that you need iojs or node --harmony for that. I generally switch over with nvm and then use node --harmony $(which npm-org-rights).

@rreusser
Copy link
Member Author

Awesome, thanks! Yeah, just trying hard to push some of this tedious organizational stuff forward. I'll see if I can set that up.

@mikolalysenko
Copy link
Member

Ok! It is done. I added all you guys to scijs using npm-org-rights. You all should do the same!

@mikolalysenko
Copy link
Member

The syntax for that command is:

npm-org-rights scijs rreusser
npm-org-rights scijs planeshifter
npm-org-rights scijs mikolalysenko
npm-org-rights scijs jaspervdg
npm-org-rights scijs hughsk

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

5 participants