Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Help wanted - apply within #162
Let me introduce myself - I'm Daniel, and I've been maintaining for Imagick for two years. Although I'm (just about) capable of doing the bug fixes and code changes needed to make Imagick work against new versions of PHP, I'm really struggling to keep the documentation up-to-date, and I don't have anywhere near enough time to improve it to where it needs to be.
Does anyone want to contribute to this project? If so, super awesome! If not - well okay, but I'm not going to care about people whining about the documentation....
The main things that need to be done to document Imagick well enough for people to start migrating to ImageMagick 7 rather than ImagickMagick 6 are:
A good example of this is all of the functionality relating to setImageBias has been migrated to the morphology function
So, is there anyone out there who uses Imagick that has the time and the desire to contribute something back? If so, either get in touch through this issue, or talk to me on twitter https://twitter.com/MrDanack or email email@example.com
If you say whether you want to contribute:
That would let me know which direction to point you in.
But in general the open tickets are on this repo's issues, and the PHP bug list:
@eallenOP sorry for the slow response and thanks for the offer. Realistically though, unless they have experience with either Imagick or ImageMagick, people who are newish to programming aren't going to be in a position to offer that much assistance without at least some guidance..
What I really need is someone who uses the library a lot, or who uses ImageMagick itself, to be able to figure out what bug reports mean, or what the changes upstream are, and so tell me what changes need to be made.
referenced this issue
Nov 29, 2016
referenced this issue
Jan 18, 2017
referenced this issue
Feb 5, 2017
Hey! First of all, I appreciate all the work you've done on Imagick. Now, let me introduce myself very quickly.
I've been using Imagick for many years now in a system that has to render big print files (that go up to 12 000px wide and more). Imagick has always worked well for us since the system is PHP-based. Not only do we actively use it (the system renders thousands of print files everyday), but we also regularly develop new stuff that uses imagick.
We've been doing a few tests recently with ImageMagick 7 and ran into problems. That's when I found this post. I'd be interested in contributing (on all aspects)! I'm certainly not an ImageMagick expert, but I've developed quite a bit of code with Imagick and done quite a lot of research on ImageMagick itself.
Let me know what you think!
Just some more info, we use Imagick on both Windows and Unix-based servers, 32bit and 64bit, if that can help with testing.
Thanks for the offer - I gratefully accept!
A really good place to start helping would be with the documentation issues that need addressing, or just in general going through the entries in http://php.net/manual/en/book.imagick.php and finding any entries that have either no info, or could do with more info.
For example some issues that could do with some writing for are:
The editor is online at: https://edit.php.net/ though it can be easier to click 'edit page' in the top right, to jump straight to editing a page. Just in case someone else doesn't accept the changes you make there, if you use anonymous login, and remember either what userId you are, or what the 'patch' name is when you save it, and ping that to me, I should be able to merge them.
Additionally, starting a migration guide for users going from ImageMagick 6 to 7 would be a big task that needs doing.
If you have any reproducible errors, please open an issue for those.
Thanks for all that info, started going through it.
As for writing the migration guide, I should be able to help with that once I start looking into migrating my own system.
I plan on continuing on any clarity fixes and filling out any function/api references that are missing or not filled out (pretty much anything @Danack mentioned above that needs help, as I'm able)