Voting is now open for the community-elected At-Large board seat!

If you’re a member of the Drupal Association as a Ripple Maker, check your inbox for a ballot from Helios voting bot with the subject line “Vote now: Drupal Association 2026 At-Large Board Election”.

Voting closes on 14 August at 23:59 UTC.

You can learn more about the 8 great candidates here: https://www.drupal.org/association/board/elections/election-2026-dates-and-candidates

Happy voting! 🗳️

I've been building with Drupal for many years now, especially in secure environments, and can't help thinking that over time the need to use additional tools to maintain it has dramatically increased.

Drupal used to be much more simple to build & administer when tun locally first then deployed, but now community notes assume you use Drush & Composer, which aren't really necessary if you know PHP dev & MySql administration.

I can't help thinking that the additional management tools mostly serve to help someone track how & where people are using Drupal by reporting specific build/deployment info & dev activity...

I haven't evaluated the add-ons yet, but may have to, because I regularly assure my clients their data and IP is safe. Also, running certain tools in firewalled environments causes a lot of issues & often requires whitelisting. If there are security gaps, we'll need to shift to a different solution, kust on principle alone.

It's important for Drupal to be fully transparent about what they monitor.