jimp
jimp copied to clipboard
Is this project dead?
There seems to be a flood of unmerged PRs, no action on behalf of the owner for over a year, and the last release was two years ago. Is there an actual currently developed fork of this somewhere? It's a shame to lose a valuable alternative to sharp.
I would hope not, I still use jimp often.
Looks to be the case unfortunately
same I am stuck on upgrading to webpack 5 as well.
I remember years ago the author being extremely strapped for time, and eager for new contributors.
Hopefully someone can help keep this project moving forward. I absolutely love it. It's an extremely valuable alternative to Sharp.
Just tossing this out there. @oliver-moran would you be willing to start a Kickstarter, to try to raise some money to put you back to work on this project?
I absolutely love Jimp, and I'd personally be willing to kick in some money to try to keep it moving forward.
I'd donate to the cause as well. Maybe even help out with some code here or there. Although I don't think @oliver-moran is around Github anymore. Maybe we should consider doing a fork sooner or later.
Hey all - one small update. I pinged Oliver (publicly) and this was his response, so if anyone is interested in being a contributor, sound off here, and he might add you. (I'd love to help but I know absolutely nothing about this project - I just adore being able to resize images in a Lambda function without pulling in huge binaries, like with Sharp)

Hey, everyone. Thanks for opening this thread – and apologies I haven't been able to keep up with the work here.
Adam, I note your response above, but if it's OK with you could I lean on you to guide me as to what the community needs me to do to get things unblocked? In essence, I would like to hand this project wholly over to the community in a way that's both secure and sustainable going forward.
It's been a joy to have started something that's both widely used and brings happiness to other people in the same way it did for me.
@oliver-moran basically find someone you trust to drive the project forward, and grant them commit access to the project, and npm access to cut new versions.
A year or two ago you added me as a contributor, but I haven't been able to help much since I .... don't really know anything about image manipulation code. At all. LOL. I basically helped get some trivial PRs out.
If we have any volunteers who are able and willing to try to maintain this project, sound off
how is this now? are we going forward?
I see that v0.16.2 was released a couple of months ago, so the project clearly isn't entirely dead. Is this issue still needed?
Hey @oliver-moran I've sent you a message on twitter on how to move forward with maintenance on jimp. In short:
We need to move the repo from under @oliver-moran's account to a shared org to make collaboration easier.
For that I've made https://github.com/jimp-dev
After a little break I'm happy to facilitate maintenance on the project. I'm also willing to help new maintainers hop on board. I myself do not plan on adding too much though.
@hipstersmoothie - don't forget the npm keys, so others can cut releases. That's the key piece. Ya'll could just fork the repo anywhere you want, but you wouldn't be able to publish.
I’m an owner of the npm package 👍🏼
And now it's in the org 🎉 Going to close out this issue and some other and put out a new call for maintainers
@hipstersmoothie ah! So sorry to tell you things you already knew.
Stoked to see this project moving forward again. Thank you so much for the work you're putting in!
https://github.com/jimp-dev/jimp/issues/1128