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

Adding new npm maintainers #77

Closed
nolanlawson opened this issue Jul 12, 2015 · 11 comments
Closed

Adding new npm maintainers #77

nolanlawson opened this issue Jul 12, 2015 · 11 comments

Comments

@nolanlawson
Copy link
Member

I've been slow to respond to issues recently, mostly due to going on vacation for the past few weeks.

I'd hate to see progress stalled on this project due to my own lack of free time, so if the other maintainers could please post their npm usernames here, I'd be happy to add them as npm authors so that they can publish. :)

@rsutphin
Copy link
Collaborator

I'm rsutphin there, too.

@rsutphin
Copy link
Collaborator

Thanks for the trust, btw.

@broerse
Copy link
Collaborator

broerse commented Jul 13, 2015

👍

1 similar comment
@OleRoel
Copy link
Contributor

OleRoel commented Jul 16, 2015

👍

@nolanlawson
Copy link
Member Author

@rsutphin You are an owner in npm now. Great power, great responsibility, yada yada. 😉

My only advice is to use your best judgment and look for +1s from the community before merging something. I'm happy to advise on PouchDB-related issues, but I admit that I haven't used Ember in a long time, and so I'm really out-of-date with changes in Ember Data. At work, we use React and YUI, and in my personal projects I'm mostly using Angular or raw DOM, so that's another reason I'm not able to keep up.

I'm really touched and honestly kinda blown away by how the community really picked up this plugin and ran with it. I think it's a testament to the Ember community; I've never seen any other group so eager to roll up their sleeves and make one of my libraries better. At some point, if I really drop off the face of the Earth, I'd be happy to create a Github organization or something so that it's no longer under my name, but I'll let you all be the judge of when it's time to do that. :)

Thanks so much, and awesome job to everybody involved.

@OleRoel
Copy link
Contributor

OleRoel commented Jul 16, 2015

@nolanlawson Sad to hear that you take a step away from this repo, but after I've stumbled upon your name in blogs and GitHub related projects so often lately I was thinking this guy has either no free time or owns a second parallel universe where he can load balance some tasks. Thank you for the Ember plugin, it is a key component of a project I am working on.

@rsutphin Good to hear that you take responsibility for npm. I am really confident that you are the right guy for this.

@nolanlawson
Copy link
Member Author

@OleRoel That parallel universe is called my personal life, which I basically haven't had for the past year or so. ;) Thanks for understanding!

@rsutphin
Copy link
Collaborator

I've published 2.0.2 with @OleRoel's fix for #72. Thanks again for your trust, @nolanlawson. I know we all appreciate the work you do on PouchDB itself and your other contributions (I've learned a lot from your PouchDB blog posts).

@nolanlawson
Copy link
Member Author

Thanks, and I really appreciate you swooping in to help out. :) Many people don't realize that open-source software is a full-time job (in addition to our regular jobs!), so it's so helpful when I don't have to spread myself so thin. :)

@nolanlawson
Copy link
Member Author

Leaving this issue open in case anybody else wants to be added as a npm owner. @broerse I realized I didn't even add you as a Github collaborator (my bad, sorry!), but you are one now.

@nolanlawson nolanlawson reopened this Jul 20, 2015
@broerse
Copy link
Collaborator

broerse commented Jul 20, 2015

@nolanlawson Thanks. I hope I can help out.

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

4 participants