How I learned about fetchpriority and decoding contributing to WordPress

I did some research and it looks like my first contribution to WordPress core was in version 4.9, way back in 2017. Since then, I’ve been trying to send at least one contribution to each major version. I haven’t missed one since WordPress 5.6, released in 2020.

With WordPress 6.3 on the way, it’s time to send in yet another contribution. As free time is rare, I divide the process into several parts, on different days. It goes like this:

  1. I create a new folder in my browser’s bookmarks (WP 6.3, for example);
  2. I open trac and go to the list of tickets for the next version ;
  3. I take a look around, paying attention to the Workflow column;
  4. I open tickets tagged with needs-patch or needs-unit-tests ;
  5. If the ticket is interesting I bookmark it, otherwise I just skip it. If it’s interesting, but not to the point of wanting to contribute, I “follow” the ticket by clicking on Watch this ticket, at the bottom;
  6. On another day, I open the bookmarks and try to choose some to send a collaboration;
  7. I pay attention to the feedback. If any adjustments to the code or explanation are needed, I will send it as soon as possible.

The code I sent this time is related to the fetchpriority and decoding attributes of the <img> tag, which I only found out about because I opened this ticket. I liked it so much that I opened this Pull Request on GitHub, which was incorporated into this changeset.

How about you? Have you already collaborated with WordPress 6.3? Chances are you’ll learn something cool just for the challenge. There’s still time!

Felipe Elia

Associate Director of Platform Engineering na 10up, WordPress Core Contributor, Global Polyglots Mentor na comunidade internacional do WordPress e Locale Manager na comunidade WordPress Brasil.

This Post Has 2 Comments

  1. Ramon July, 17 2023

    I follow a similar process 🙂

    In the last contribution, I learned that test methods with multiple assertions should have a final $message parameter at the end of each assertion to provide context.

    1. Felipe Elia July, 17 2023

      Interesting, @Ramon, I didn’t know that yet. Instead of writing
      $this->assertInstanceOf( 'stdClass', $prepared );
      we should use
      $this->assertInstanceOf( 'stdClass', $prepared, 'The item could not be prepared for the database.' );
      right? (I went to the PR you sent to make sure I understood it right.) Thanks for the comment!

Comments are closed.