-
Notifications
You must be signed in to change notification settings - Fork 3
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
Maintain #8
Comments
Yes! I would love to give it to you. As a first step, I can transfer the GitHub repo to you. I transfered a puppet module to someone else before, but if I remember correctly, we did not find a way to transfer ownership in PuppetForge. If you know how to do that, let me know. |
Sorry for the late reaction. I have build a lot of puppet modules, but i haven't published any yet to the puppetforge and do not have any experience in publishing them to the forge. I will dive in to that |
Hey @Fabian1976, are you still interested in taking over the ownership of this module? I'm currently in the process of transferring the other module completely, see the discussion here heini/puppet-wait-for#11 (comment). TL;RD: Once you have published the module once under your name, it seems we can raise a ticket with Puppet labs to deprecate the one published under my puppetforge account. If you are still interested, I would first start by transferring the GH repo to you. Let me know what you think. |
Hello Bastian,
I am still interested in taking over this module to update/maintain it. I already have an account at puppet forge, so I can easily build and upload a newly build module.
|
I requested the repository to be transfered to you. After that, you should publish it under your own forge account and then raise a Jira ticket at Puppetlabs like this one: https://tickets.puppetlabs.com/browse/MODULES-7464. That should be all. Thanks for stepping up. |
Hello,
We are using this module. Can we maintain it as well?
The text was updated successfully, but these errors were encountered: