-
Notifications
You must be signed in to change notification settings - Fork 64
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
state of cookbook #132
Comments
Maybe @chef-brigade would be willing to take over? |
If someone is willing to keep on top of pull requests for this cookbok, I'm happy to support them with chef brigade stuff. Mostly, we just make sure that there's someone with release authority for each cookbook, all maintainers are owners. We'd really prefer to have @RiotGamesCookbooks and @KAllan357 bless it. If you want us to maintain websites, support chat rooms, build infra; we're happy to provide that even without moving over to chef-brigade officially. I've worked with this cookbook in the past, long ago, but I don't use this in any capacity any more. |
@dzabel @fletchowns would either of you be willing to handle incoming pull requests? If so, I can start transferring this cookbook to chef-brigade. |
@josephholsten before transfering the cookbook to someone else, we have to talk about nexus_cli gem. Some of the incoming pull requests can only be merge in conjunction with a pull request for the nexus_cli gem. |
@KAllan357 I do have the same question. Any chances of open pull requests being reviewed and merged. Looking at the current state, even the current version of the cookbook is not published in supermarket. |
@RiotGames is @KAllan357 still working for you - did you still use nexus? |
@KAllan357 - any chance fr a new release with merged in pull requests?
Maybe you can open the cookbook for adoption?
The text was updated successfully, but these errors were encountered: