Consider switching from imagemagick to vips
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Mastodon recently began the switch to vips as it is apparently faster and uses less memory https://github.com/mastodon/mastodon/issues/20269. It also has less security issues currently.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no Nextcloud files, tests, or entry points. Start by reviewing the proposed ImageMagick-to-vips change in the linked Mastodon discussion, then identify the affected server image-processing paths; done would require an agreed migration scope and evidence that performance, memory use, and security goals are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100