jwilder
Is this project still maintained or abandoned ?
There are 14 open PR and 25 Issues with no real activity from the maintainer for quite a while.
Just trying to understand if is worth trying to merge my changes back in
See https://github.com/jwilder/dockerize/issues/120#issuecomment-443442786
@fknittel Thank you, that helps a lot
@jwilder based on the comment linked above, is there a process you would like about pull request to this project ? Maybe a discussion before a PR is opened ?
When looking at github projects i find it very upsetting to see an high number of pull requests open that have no comments and have not been closed because maybe they did not fit the project for some reason.
In my case i was simply looking after an option to set insecure tls when checking an https endpoint ( Mostly for self signed certificate in a kubernetes cluster ) and indeed ended up with my own fork .
thanks!
Happy new year to everyone!
@jwilder do you need help with the maintenance of this project? I've gone through most of the pending PRs, commented on ones I felt needs commenting. I'd be happy help out more if there is a way to speed the release cycle up.
A few general ideas I have that would improve the workflows of the project in the long term:
- Use Go modules
- Use GitHub Actions to automate CI and release processes
Some of the outstanding issues that needs fixing IMHO:
- arm64 builds
- static builds in docker
Adding the sprig library would also be nice in my opinion. One issue I faced recently: quoting values in a YAML config file.
I'd be happy to send a few PRs addressing those or resubmit PRs (considering some of the above already have PRs). I'd also be happy to help out as a maintainer if you don't have the time to maintain this project anymore.
I'm not usually one to push on these kind of things, but I agree that a new maintainer is needed here, even if just for intermittent updates.
I don't mean to sound rude, but for a tool linked from the official Docker docs, my experiences so far have been overwhelmingly painful. Even trying to build the container from the current HEAD fails without #132
I think this tool still provides a large value to the Docker ecosystem when containerizing legacy applications. It's sad to see it unmaintained.
For anyone else who stumbles upon this, as implied in https://github.com/jwilder/dockerize/issues/120#issuecomment-443442786 this project has already been forked over at https://github.com/powerman/dockerize. Be wary of the changes, as many of the PRs currently still open have been merged, so the code base is quite significantly different and will require some testing to validate the logic.
The concerns of jwilder are valid, but having an unmaintained project is not something most can work with.
In that case, I feel we should notify the docker team to either update their docs to the powerman repo or remove it outright.
I created an issue/PR in their repo above.
