Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Need any new co-maintainers? #106

Closed
patcon opened this issue Jul 7, 2015 · 4 comments
Closed

Need any new co-maintainers? #106

patcon opened this issue Jul 7, 2015 · 4 comments

Comments

@patcon
Copy link
Collaborator

patcon commented Jul 7, 2015

No pressure. Just curious. I prefer to operate within a process where nothing gets merged until there's a +1 vote of confidence from a co-maintainer, so you wouldn't have to worry about me going overboard :)

(And fwiw, in case you're looking at my PR's and not liking them, I'll admit that I tend to be way more liberal with my PR's changes when I'm not the maintainer. When I am a maintainer, I feel less pressure to get multiple things into single PR's, as I can merge my own individual ones once +1's have been given)

@linc01n
Copy link
Collaborator

linc01n commented Jul 7, 2015

I am thinking we need a process if we have more than 1 maintainer in this project. I like the +1 approach.

@bflad Would you mind adding one more maintainer to this project?

@patcon
Copy link
Collaborator Author

patcon commented Jul 9, 2015

Hey @bflad, I think I'm going to need push access in order to get #108 working, if you have a sec to consider. (I need push access to add the encrypted api key to travis.)

@bflad
Copy link
Owner

bflad commented Jul 12, 2015

I have granted @patcon push access just now. Thank you both!

@bflad bflad closed this as completed Jul 12, 2015
@patcon
Copy link
Collaborator Author

patcon commented Jul 12, 2015

Thanks a bunch!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants