At its core, ambush marketing is simple: one organisation pays to create attention, and another steps in and captures that attention without paying for the privilege.

Every open source project eventually faces the same danger: becoming so busy managing itself that it forgets how to move forward. The challenge is not avoiding structure altogether, but finding the smallest amount of process needed to keep a project healthy without suffocating the people who make it possible.

There is a recurring pattern in open source communities, especially around mature ecosystems like Joomla, where enthusiasm for ideas is abundant but responsibility for delivering them is not. Users frequently arrive with confident feature requests that are framed as something everyone would benefit from, but with no intention of contributing to the work required to make them real.

These, often well-meaning, requests can often change the software into something harder to maintain, harder to use, and ultimately harder to sustain.

In open source, we celebrate the visible things. New contributors joining. First pull requests. Community growth. Another release shipped. Those things are easy to measure, easy to share, and easy to feel good about.

What is much harder to see is the silence left behind when someone quietly disappears. No goodbye post. No dramatic exit. Just someone who used to be around every week suddenly no longer there.

And too often, nobody notices. Or worse, people notice and assume someone else will reach out.

Today, choosing software is no longer just about features, cost, or even whether it is open source. Increasingly, it is about something more uncomfortable: digital sovereignty. Who controls your data, your infrastructure, and your ability to leave with your data intact when things stop working in your favour?

In 2005, Joomla wasn’t launched with venture capital, a corporate roadmap, or even a clear long-term strategy. It began with something far more fragile and far more ambitious: a belief.

Open source does not work by accident. It works because people show up. We often describe that effort as "giving back." It’s a useful idea, but it may also be limiting how we think about contribution.

With Joomla 6.1, a small but powerful enhancement was added to the TinyMCE editor: dedicated buttons for inserting, editing and removing the HTML <abbr> element.

The 80/20 rule isn’t just some nice talking point for economics class. It’s real, it’s brutal, and it applies perfectly to software development.