-
Notifications
You must be signed in to change notification settings - Fork 120
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
Project Status: Unmaintained and looking for a new maintainer #127
Comments
Congrats on the full-time role! I've been using the linuxserver/grocy image for a bit, mainly because dockstarter after I was maxing out my pi with HA. While I'm not Docker savy enough to take the full load, I'd be happy to help when I can. |
Thanks @Rollins-Star. Taking a look through the list of open issues and pull requests could be a good way to get started - and/or you're welcome to suggest additional changes to the project. |
Thanks all for the work put into this and also my best wishes for your new job @jayaddison! Unfortunately can't help personally since I'm still not into the Docker world for anything... |
Thank you @berrnd - and no problem. Ideally I'd like to keep my maintainer privileges here for a little while, at least until we have one or two more contributors. That said, I'll be glad to have those removed when they're no longer required. |
I only recently started using grocy and grocy-docker. But I think I have a fair amount of experience with docker (and related technologies such as podman). I also have a full time job and usually don't have a tremendous amount of time, but I can probably help to distribute the maintenance burden across more shoulders (I already opened some merge requests). |
Much of the release process for |
Hi @berrnd - I think I should take a break from maintaining If I manage to get those focus levels back, maybe I'll return! I hope that someone may be able to pick up maintenance from here (although perhaps I haven't documented enough of the processes). |
Hi @jayaddison, that's fine and no problem at all. Maybe add a note to README or pin this thread if you want. In any case I can't take this over, simply since I'm still not into Docker at all. But from what I've heard, the alternative linuxserver/docker-grocy also works just fine. Thanks a lot for all your time you put into grocy-docker and all the best! |
You're welcome - and yep, those are good suggestions. Thank you! |
Ok, README updated, with a reference to this (re-pinned) issue. I'll drop my maintainer/organization privileges in a few moments (edit: done). |
Having recently taken on a full-time employment role (that I'm enjoying), there's a bit less maintainer time available for
grocy-docker
at the moment, meaning less time to discuss inbound issues, technical direction, review pull requests, and generally improve the shape of the project.Does anyone have suggestions about how to find and on-board potentially interested contributors so that I could bow out at some point?
Alternatively, should
linuxserver/grocy
become the one true containerizedgrocy
?cc @berrnd
The text was updated successfully, but these errors were encountered: