Category: Open Source

  • Minor But Mighty: elevating WordPress one minor release at a time

    Minor But Mighty: elevating WordPress one minor release at a time

    WordPress 6.8 “Cecil” shipped earlier this month, and with the new once-a-year major release cadence, there will not be a WordPress 6.9 until sometime next year.

    That gives us a rare opportunity: let’s rally as a contributor community and give these 6.8.x minor releases attention more akin to major releases.

    WordPress’ minor releases aren’t just for emergency fixes; they’re a real opportunity to focus, polish, and improve WordPress in specific ways.  The following are some ideas I have on different focuses we would have with 6.8.x minor releases.

    1. Good First Bugs Blitz

    We’ve got a backlog of “good first bugs” that already have patches, so let’s get them tested, reviewed, and committed.  Clearing these builds contributor confidence, keeps the door open for new contributors, and reduces technical debt.  It’s a win for the project and the community.

    2. “Paper Cuts” (aka UX polish)

    Tiny friction points add up.  Let’s fix the little annoyances that get in the way of a great editing and admin experiences.  (No formal query for this, just a call for suggestions on what little nags or pet peeves folks have that could use some small tweaks.) Not every improvement needs to be huge; removing friction in the basics makes WordPress feel smoother, faster, and more welcoming for everyone.

    3. Accessibility Improvements

    I would love to partner with folks like Amber Hinds, Joe Dolson, and others to ship a release centered around accessibility improvements.  Accessibility isn’t optional.  It’s core to WordPress’ mission of democratizing publishing for everyone, and these improvements help real users every single day.

    4. Internationalization + RTL Support

    There’s room to improve for non-English (“I18n“) and Right-to-Left (“RTL“) language users who often times get forgotten behind focuses on “American” and “English” support.  English speakers aren’t the majority on the internet.  Improving i18n and RTL support makes WordPress better for millions, not just a handful of users.  Let’s make the platform more global in practice, not just in theory.

    5. Bundled Theme Improvements

    Let’s continue upgrading default themes to better reflect today’s block editor capabilities, maybe even revisit Post Formats in the process.  Modernizing bundled themes keeps WordPress feeling current and shows off its best capabilities right out of the box.

    6. Privacy Enhancements

    There’s plenty to work through in the Privacy component, we can help ship thoughtful improvements that matter.  Privacy expectations and regulations keep evolving.  WordPress should continue empowering users to control their own data and stay ahead of the curve.

    7. PHP Compatibility Focus

    PHP 8.4 is here and some hosts are upgrading fast, so let’s keep WordPress running cleanly, consistently, and compatibly across current, active PHP versions.  Staying compatible means better performance, better security, and better future-proofing for sites around the world.

    9. Security Fixes (Always)

    Security fixes will of course stay a priority, so in so far as there are things folks can help within the Security component then let’s do it.  WordPress powers a huge portion of the web, and with great reach comes great responsibility.  Regular security work protects users, businesses, and the open web.

    Why These Minor Releases Matter

    Every improvement we target from accessibility, internationalization, privacy, PHP compatibility, security, UX polish, to contributor experience strengthens WordPress in ways that matter today and even more tomorrow.

    This isn’t just “maintenance”, it’s about doing the work that keeps WordPress usable, reliable, trusted, and welcoming for the next generation of users and contributors.  6.8.x gives us a real window to focus without the distractions of a major release.  We should take advantage of it.

    Not flashy.  Not headline-grabbing.  Just meaningful progress, the kind that sticks.

    If you’re interested in leading, patching, reviewing, testing, or just helping shape what comes next, let’s talk.  Let’s ship real improvements, together.

    Let’s Do This Together

    I’d love to lead (or co-lead) a few of these minor releases.  But I’d also love to see others step in.

    • Want to lead a focused minor release?
    • Want to contribute through patches, reviews, or testing?
    • Have a new focus idea that fits the spirit of targeted, impactful updates?

    Say something.  Step up.  Let’s get organized and make it happen.

    Comment here, or ping me in WordPress Slack (I’m @jeffpaul there).  Let’s ship some solid stuff in 6.8.x and keep WordPress moving forward. ????

  • Why I Wrote a Personal README (and Why You Should Too)

    Why I Wrote a Personal README (and Why You Should Too)

    I value transparency, collaboration, and clarity whether that’s working with colleagues, contributors in the WordPress community, or clients.  But one thing has become clear over time: everyone works differently, and understanding those differences upfront makes for smoother, more effective collaboration.  Enter the Personal README.

    Inspired by Luc Levesque, Roy Rapoport, and 18F’s guide on Personal READMEs, I put together my own as a way to share how I work, communicate, and approach leadership.  It’s a snapshot of my work style, values, and expectations, both for myself and for those working with me.

    ???? Check it out here: jeffpaul.com/readme/

    Why Write a Personal README?

    A Personal README isn’t a set of hard rules, it’s a tool to set expectations, remove ambiguity, and help others understand how to best work with you.  It can cover things like:

    • Your working hours and communication preferences
    • Your approach to meetings and collaboration
    • What makes you excited (and what chafes you or makes you grumpy)
    • How you give and receive feedback

    By being upfront about these things, you can reduce friction and make it easier for colleagues to engage effectively.  It also helps new team members ramp up faster, since they don’t have to guess what works best.

    My Challenge to You

    If you haven’t written a Personal README yet, I highly encourage you to give it a shot!  Start with something simple and iterate over time.  Ask yourself:

    • What’s important to me in how I collaborate?
    • What do I expect from my teammates?
    • How do I like to communicate and make decisions?

    And if you do create one, share it!  Put it in your profile on social networks and communication platforms as well as your personal website (you own your own content right?!), basically wherever people can easily find it.  The more we normalize transparent communication, the easier it becomes to work effectively together.

    If you already have a Personal README, I’d love to see it!  Drop a link in the comments or tag me on Bluesky / Mastodon / LinkedIn or wherever we connect.

    Let’s make working together easier. ????

  • Contributions Welcome!

    Contributions Welcome!

    Josepha Haden lead a panel discussion at WordCamp Montclair earlier this summer with Michelle Frechette, Courtney Robertson, and Ebonie Butler on the topic of the all women and non-binary release squad in WordPress 5.6 (aka “Simone”) and their individual and shared experiences contributing to WordPress.  One of my favorite parts was when Josepha stresses what should already be a certainty, but unfortunately one that still bears repeating (and amplifying); namely that contributions from anyone should always be welcome.

    The clip below highlights that part of the panel discussion and shows off Josepha’s wonderfully quirky approach storytelling.  Please watch and consider sharing in your networks so we can ensure this approach to welcoming all contributions spreads as widely as possible.

    Fediverse Reactions