Skip to content

Pull Request for additions to the ImageMagick Section#487

Open
LUCIA224 wants to merge 9 commits intoamiaopensource:gh-pagesfrom
LUCIA224:gh-pages
Open

Pull Request for additions to the ImageMagick Section#487
LUCIA224 wants to merge 9 commits intoamiaopensource:gh-pagesfrom
LUCIA224:gh-pages

Conversation

@LUCIA224
Copy link
Copy Markdown

@LUCIA224 LUCIA224 commented Dec 18, 2025

Checklist

This pull request includes additions to the ImageMagick section of ffmprovisr.

Comment thread index.html
Comment on lines +2971 to +2983
<label class="recipe" for="im_fconversion">Format conversion</label>
<input type="checkbox" id="im_fconversion">
<div class="hiding">
<h5>Format conversion</h5>
<p><code>convert <em>input_file.png output_file.jpg</em></code></p>
<p>Converts a file from one format to another.</p>
<dl>
<dt>convert</dt><dd>starts the command</dd>
<dt><em>input_file.ext output_file.ext</em></dt><dd>takes the input file format and converts it to the output file format. Although this example uses .png to .jpg any format conversion combination can be used so long as the formats are supported by Image Magick.</dd>
</dl>
<p> ★ImageMagick V7 command: <code>magick <em>input_file.png output_file.jpg</em></code></p>
<p class="link"></p>
</div>
Copy link
Copy Markdown
Member

@kfrn kfrn Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello! thank you for the contribution 😸

These changes look good overall, but would you mind to indent the markup correctly, as in the other recipes?

(also below)

Comment thread index.html
<div class="hiding">
<h5>Control the compression quality of an image</h5>
<p><code>mogrify -quality value image_file.ext</code></p>
<p><p>Controls the compression quality of JPEG, PNG, HEIC, and WebP image files.</p>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume, there is a <p> too much at the beginning?

@kfrn
Copy link
Copy Markdown
Member

kfrn commented Apr 14, 2026

I wanted to bump this one - @LUCIA224, are you still around?

@jmf-nyu
Copy link
Copy Markdown
Contributor

jmf-nyu commented Apr 15, 2026

@retokromer @kfrn Thank you for taking the time to review this PR. I’m also commenting as the professor of the students who submitted it. I hope you will take into consideration that this is their first ever contribution to a project on Github and they’re still learning both the technical and collaborative aspects of the process.

Given the timing in the semester, they may not be able to address these issues quickly. If it’s feasible for you to make the small adjustments, that might be the most efficient way to move things forward. Otherwise, I’m happy to create a new branch and submit an updated PR myself.

Please let me know what works best for you.

@kfrn
Copy link
Copy Markdown
Member

kfrn commented Apr 16, 2026

@retokromer @kfrn Thank you for taking the time to review this PR. I’m also commenting as the professor of the students who submitted it. I hope you will take into consideration that this is their first ever contribution to a project on Github and they’re still learning both the technical and collaborative aspects of the process.

Given the timing in the semester, they may not be able to address these issues quickly. If it’s feasible for you to make the small adjustments, that might be the most efficient way to move things forward. Otherwise, I’m happy to create a new branch and submit an updated PR myself.

Please let me know what works best for you.

Hi @jmf-nyu, yep I hear you on the fact that these students are new to this, and we keep that in mind when reviewing - perfection is not a requirement 😀

However, communication + the work being in a mergeable state is. The student who made this submission did not acknowledge neither my nor Reto’s review comments back in December, and has not commented subsequently. In open source, as in life, we need communication in order to move things along. The submitter participating in this feedback loop is an essential part of the OS contribution process.

Going forward, here is what would work best for us:

  • Please ensure that students know that submissions being merged as-is is not a given
  • Please ensure that students know that they may receive reviewer comments, and that they will need to engage with those and participate in the feedback loop
  • Please guide students to submit changesets in line with the Guidelines for Contributing (recently updated)
  • We appreciate your position, but it is more appropriate for the submitter to respond directly. That needs to happen here in order to move forward with this specific PR, and it is also our general expectation.

Maintaining this project is something that we do for free, for community benefit, and we ask that contributors respect our time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants