-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
Make use of "percona" namespace on Opscode community site #16
Comments
@patcon that works for me. Let's also see how this plays out with regards to customink-webops/percona-install#6. Thanks for the interest! |
No sweat. I'll just cc these guys, as they have possession of the namespace //cc @dje @heavywater |
Works for me. What's the Opscode user name that will take over the cookbook? |
Thanks @dje! How about adding @phlipper, @nathenharvey & myself? We can figure out the details once we get talking :) Obviously, if you guys at heavywater are still using it, it would be great to get your input as well. |
Added those accounts. Let me know when one should be promoted to "own" it I suppose. I don't think we ever used it beyond my personal needs. I believe it's effectively abandoned at this point. I'd be happy to see a well maintained code base take its place. |
that's awesome. thanks again @dje |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
While I'm here, what are your thoughts on asking the current maintainers of the "official" percona cookbook on the community site, to see whether they'd be amenable to handing the namespace over to you?
http://ckbk.it/percona
It seems your cookbook is much more active and general, and it would only make sense. I imagine they'd be able to see that.
Would you be interested if they were? I can get in touch.
The text was updated successfully, but these errors were encountered: