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

add maintainers? #232

Closed
michaelglass opened this issue Oct 11, 2013 · 15 comments
Closed

add maintainers? #232

michaelglass opened this issue Oct 11, 2013 · 15 comments

Comments

@michaelglass
Copy link

@michaelglass michaelglass commented Oct 11, 2013

Hey there! This repo is broadly used and has a lot of activity. What say you to adding a few maintainers?

@routelastresort
Copy link

@routelastresort routelastresort commented Oct 28, 2013

👍

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Nov 6, 2013

Hey @michaelglass yeah I would agree there. Been slacking lately and finally carving out time to give this some more attention. Would be up to @fnichol there on adding maintainers.

@miketheman
Copy link

@miketheman miketheman commented Dec 21, 2013

On this note, how about releasing a newer version than 0.0.4 to the community site?

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Dec 27, 2013

Since we've got the namespace available, the plan is to cut a 0.9.2 release from the current master. The future of the cookbook will start with an LWRP refactor #235 that drops the rvm gem dependency entirely. Hope to start clearing up a lot of these issues and get this cookbook back on track once again.

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Dec 27, 2013

As far as I can tell its just myself and @fnichol here so it would be up to him to add additional maintainers. I have deferred a lot of the decision making to him since its his cookbook.

@michaelglass
Copy link
Author

@michaelglass michaelglass commented Dec 29, 2013

appreciate the work in general, @martinisoft

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Dec 29, 2013

Thanks @michaelglass I'm sure the new year will bring some renewed effort into getting a lot of these issues resolved.

@fnichol
Copy link
Contributor

@fnichol fnichol commented Dec 30, 2013

I so agree with this one 😄

Going forward into the new year I'd love to transition maintenance and development of this cookbook to those in the community who use it day in and day out. @martinisoft bravely stepped forward and I couldn't be happier for the help (thank you, thank you, thank you).

It looks like we (finally) have a solution for moving the codebase forward in a sustainable way that should survive new and different upstream behaviors in future releases.

If @martinisoft and I can get a fixed release out with a general direction set then we should be ready for other members to come on board with commit bits. Sound reasonable?

@RKushnir
Copy link

@RKushnir RKushnir commented Sep 8, 2014

Is this repo still maintained? Looks like there's been only cosmetic changes to the code lately.

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Sep 9, 2014

@RKushnir we'll be making some big changes in the next couple of weeks. I highlighted them in a blog post

@martinisoft
Copy link
Contributor

@martinisoft martinisoft commented Sep 9, 2014

Short answer, yes there will be maintainers added soon past the 1.0 release.

@RKushnir
Copy link

@RKushnir RKushnir commented Sep 9, 2014

@martinisoft thanks for reply, and the blog is quite interesting!

@damacus
Copy link
Member

@damacus damacus commented May 31, 2019

Closing due to inactivity.

If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!

Thanks,
Sous-Chefs

@damacus damacus closed this May 31, 2019
@lock
Copy link

@lock lock bot commented Jun 24, 2020

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.

1 similar comment
@lock
Copy link

@lock lock bot commented Jun 24, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants