As mentioned in #4026 by @hugovk, we could use some volunteers to help review PRs.
And since we are approaching Year 2 with Tidelift, that volunteer position could _potentially_ turn into a paid slot on the Pillow core developer team. If you are interested in volunteering, please tell us your experience with the Pillow project and why you'd like to help.
Thank you all who consider 🎉
@homm Are you in for Year 2 with Tidelift i.e. are you still actively developing https://github.com/uploadcare/pillow-simd ? If so, I have two requests:
Looks like this was your last Pillow-related activity:
As far as I can tell from that, https://github.com/uploadcare/pillow-simd is a fork of Pillow which you're using to do performance testing, with results reported to https://github.com/python-pillow/pillow-perf. That's _probably_ OK, but it would be more clear to the outside world I think if the fork of the fork (i.e. https://github.com/uploadcare/pillow-simd) were to be hosted here (and yes, I realize I just stated with sincerity that it would be "more clear if the location of the fork of the fork were to change" … perhaps only slightly more clear 😄 )
@python-pillow/pillow-team I'm moving this to In Progress now, if we don't get anyone by early 2020 let's close this and open a new one toward the end of 2020.
Hi, @aclark4life and @python-pillow/pillow-team
are you still actively developing https://github.com/uploadcare/pillow-simd ?
The majority of the work was done before I joined the Lifting program (which was 1 year ago, actually). Right now I'm working on significant improvement of .thumbnail() method in both speed and quality terms, which I hope to finish before 7.0 release (in both Pillow and Pillow-SIMD).
But as before my work is sporadic and based on my primary job's needs. I see how other team members work on Pillow improvement on a regular base and understand what my contribution is very different and may differ from how Tidelifting should look like. So I think that it is fair to opt-out of the program.
Despite this, I want to stay Pillow's team member with some weight in discussions and more tolerant code reviews, as I know Pillow's internals very well.
Can we move https://github.com/uploadcare/pillow-simd to this organization?
This is doable if everyone including users could benefit.
Current problems are:
I suggest creating a new chapter in the documentation about Pillow's performance where a large part will be about Pillow-SIMD with information about Uploadcare supporting (as no one else still contributed anything in Pillow-SIMD itself). I think a good start is Pillow-SIMD's README page.
I have an idea of how other problems listed above could be solved, but this is part of another topic.
Thanks @homm , all sounds good to me, thanks for your previous and continued support! If you ever feel like you want to jump in again as "paid volunteer", please let us know.
@kszu can we drop @homm from Tidelift starting Jan 1 2020? Looks like we'll drop to a 4-person team at that point (me, @wiredfool , @hugovk , @radarhere ) and continue to split payments from Tidelift evenly,. Thank you!
Yes, we can certainly do that! Thank you for letting us know.
It's been a pleasure working with you @homm ! We'll make our final payment to you in January (accounting for December). Please reach out if you have any other questions!
@aclark4life @homm now that the December 2019 payout run is complete I've removed @homm from lifting and adjusted the monthly payment split accordingly. Please let me know if I can help with anything else and thank you!
/cc @kszu
Most helpful comment
Hi, @aclark4life and @python-pillow/pillow-team
The majority of the work was done before I joined the Lifting program (which was 1 year ago, actually). Right now I'm working on significant improvement of .thumbnail() method in both speed and quality terms, which I hope to finish before 7.0 release (in both Pillow and Pillow-SIMD).
But as before my work is sporadic and based on my primary job's needs. I see how other team members work on Pillow improvement on a regular base and understand what my contribution is very different and may differ from how Tidelifting should look like. So I think that it is fair to opt-out of the program.
Despite this, I want to stay Pillow's team member with some weight in discussions and more tolerant code reviews, as I know Pillow's internals very well.
This is doable if everyone including users could benefit.
Current problems are:
I suggest creating a new chapter in the documentation about Pillow's performance where a large part will be about Pillow-SIMD with information about Uploadcare supporting (as no one else still contributed anything in Pillow-SIMD itself). I think a good start is Pillow-SIMD's README page.
I have an idea of how other problems listed above could be solved, but this is part of another topic.