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

Open up project ownership #16

Open
jsok opened this issue Feb 17, 2016 · 9 comments
Open

Open up project ownership #16

jsok opened this issue Feb 17, 2016 · 9 comments

Comments

@jsok
Copy link
Owner

jsok commented Feb 17, 2016

At this point I'm merely the original author, most of the code as it exists now has been contributed by the community (thanks all! 🎉 🎈)

I'm keen to add another contributor or two to both the GitHub repo and the rubygems project.

Reference:

@jsok
Copy link
Owner Author

jsok commented Feb 17, 2016

@abooitt would you like to become a project owner?
@nickithewatt I know you are actively using the gem too, would you like to take part ownership or able to recommend someone else?

@jsok jsok changed the title Add another contributor Open up project ownership Feb 17, 2016
@abooitt
Copy link
Contributor

abooitt commented Feb 17, 2016

Hi @jsok, thanks for the invitation. I am interested. Will discuss at my work.

@nickithewatt
Copy link

Hi @jsok, been on holiday so sorry for the delayed response, thanks for opening it up. Let me chat with our guys this side and see what may be on the cards!

@devopsbrett
Copy link

Hi @jsok, I work at OpenCredo with Nikki.
This is a great gem and we would love to help with ownership of this project.

@abooitt
Copy link
Contributor

abooitt commented Jun 2, 2016

Hi @jsok, unfortunately I do not have time to take ownership. However, I do look forward to get #10 released. We have the functionality in there in production. So, I am willing to spend some time on getting it publicly available, working together with @nickithewatt and @devopsbrett .

@devopsbrett
Copy link

Hi @jsok,
@nickithewatt and I would be happy to work with @abooitt to help with ownership of this

@juniorsysadmin
Copy link

@jsok I'm not speaking on behalf of anyone, but have you considered moving the module over to Voxpupuli https://voxpupuli.org ?

@davealden
Copy link
Contributor

@jsok Have you thought about @juniorsysadmin comment? We are getting to role out a new puppet infrastructure that is going to rely heavily on this module and we'd hate to see it die due to lack of time.

btw - thanks for taking the time to write and publish this. Even if you don't have the time to maintain it, it's been a huge help to us.

@jsok
Copy link
Owner Author

jsok commented Feb 19, 2017

Thanks for the ideas everyone. My main concern to be alleviated before opening this module up is the severe lack of tests. I've done some work on #21 to start doing actual integration tests against vault which I think is a massive win.

@juniorsysadmin @davealden yes voxpupuli looks like a good option, there's a fair bit of work in the migration so I'll have to research that process a bit more.

@nickithewatt @devopsbrett if you want to directly move things forward, PRs which improve the testability of this module would make me more confident in opening it up to more owners.

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

6 participants