What Bram Driesen Sees from Inside the Drupal Ecosystem

Most people in open source talk about the power of community. Bram Driesen shows up and does the work. For more than a decade, he has contributed to Drupal by building systems, leading local groups, mentoring new contributors, and capturing the energy of events through his lens. He does not draw attention to himself. He does not have to.

Bram’s career in web development began like many others, grounded in PHP and complex e-commerce platforms. What set him apart early on was not just technical skill but his disciplined approach. He has always cared about structure, clarity, and doing things the right way. That mindset led him to Drupal, where he found a technical framework and a community that valued the same principles.

When asked why he has stayed committed to Drupal for so long, Bram puts it plainly:

“The community. It’s amazing to see the drive behind everything related to Drupal.” 

That might sound simple, but it reflects how he operates. He has helped organize events big and small, from local meetups in Belgium to Drupal Developer Days 2025. He sees volunteerism as the invisible engine behind open source. 

“People tend to forget that behind almost every single Drupal Event, including DrupalCon is a huge team of volunteers to make things happen.”

He does not just build with code. Bram is also a photographer who documents Drupal’s people and moments. What started as a side hobby turned into something much more when he answered a volunteer call at DrupalCon Prague in 2022. His photos, all released under Creative Commons, have since appeared in official blog posts and across the Drupal Association’s platforms. 

“Releasing photo’s under CC BY-SA and to see them being used in things like official blog posts of the DA or other big name companies really gives a boost,” 

he says. His Flickr gallery has now passed 900,000 views.

That sense of responsibility also shows up in how Bram talks about attribution. When he noticed The Drop Times had used his photos without credit, he reached out directly. His concern was not about personal recognition, but about reinforcing a shared standard across the open-source ecosystem. 

“People tend to forget you can’t ‘just use’ any image you find on the internet. Every piece of content on the internet, it being an image, text or code is subjected to a license.”

Following that exchange, The DropTimes worked to address the issue and improve internal practices around image use and attribution. For Bram, it was not a matter of blame but of alignment. He sees proper licensing as part of the same discipline that underpins secure code, contributor recognition, and long-term project health.

As mentioned, Bram believes strongly in structure, in how communities organize themselves, how projects stay healthy, and how contributors are recognized. That belief made him a natural fit for the Drupal Security Team, where he now serves as a provisional member. He is direct about how security should be handled in open-source systems. 

“I don’t think there really is a balance to be found. Everything security related should be reported first through the security team. If an issue can be treated in public the team will release the issue for the public to review.”

He also has strong opinions about code quality. Over the years, Bram has inherited many poorly maintained Drupal projects, and what he has found is often alarming. 

“I’ve taken over quite some projects created by different companies in my professional career. It’s baffling me that there is so many ‘hacked’ code in projects. Ranging from just a local patch with no explanation, to completely copied over and altered contributed projects in the customs module directory.” 

He believes better training around contribution workflows could make a big difference.

His technical range goes well beyond development. He has worked with analytics, SEO, and continuous integration. But what concerns him most is how easily developers forget the basics. 

“In the age of AI assisted development, I have the feeling the very basic design principles and best practices are being lost.” 

He recommends developers read The Pragmatic Programmer and Clean Code not for nostalgia, but because their lessons still hold up.

Bram also brings a rare sensitivity to team dynamics. He has worked extensively with offshore teams and understands the real impact of time zone barriers and cultural differences. 

“Timezone differences can be tricky, especially when dealing with teams on the other side of the world. Cultural differences can also be surprisingly difficult to work with in the sense that people might work totally differently then you’re used to yourself.” 

For Bram, successful collaboration requires empathy, not just planning.

He sees Drupal’s governance model as one of its core strengths. In contrast to other open-source platforms where leadership is opaque or overly centralized, Drupal’s community structure remains open and participatory. 

“There are many other open source projects looking at how the Drupal project is managed.” 

But he is not complacent. He believes Drupal must continue to improve its content editing experience and keep pace with AI integrations if it wants to stay competitive. 

“Big steps are being taken in regards to the content editor experience and AI, this needs to continue in order to stay competitive with other CMS solutions.”

Outside of Drupal, Bram is experimenting with home energy systems. He has been learning about smart home technology and energy management setups that can dramatically lower or even erase a home’s utility bill. 

“It’s possible with an EMS and home battery to reduce your energy bill of a modern home to zero or even make money,” 

he says. He sees it as more than a hobby. It is a way to apply technical thinking to practical, long-term problems.

Bram does not chase attention. He works where it matters, in the infrastructure of projects, the foundations of teams, and the quiet rules that keep communities alive. Whether it is a clean deployment pipeline, a properly credited photo, or a reminder to respect licensing, his contributions carry weight. Open source needs people who can lead without making noise. Bram just keeps showing up and making things better.