Meet Carlos Ospina — Candidate for the 2025 Drupal Association Board Election

TDT[1]: You've highlighted the need for a sustainable Drupal ecosystem in regions such as Latin America, where economic differences pose challenges to participation. If elected, how would you advocate for Drupal to adopt financial models or partnership structures that are more accessible for regions with lower economic thresholds?

Carlos Ospina: At the DrupalCon Atlanta board meeting, Tim Doyle mentioned that a parity price index is being used, which is encouraging. The problem is that this needs to be better promoted, and we need to validate its effectiveness with actual feedback from local companies.

We need to connect with potential partners that work in the local market, not just companies doing work for the same big markets from different locations. These companies have completely different perspectives because they live in different economic realities.

As I wrote in my "Creating Real Business Value" post, we need models that actually connect businesses while understanding regional contexts.

We also need regional DrupalCons, more than just simple tests, actual sustained events that develop regions locally. The fair-style or trade event approach works in many regions, where organisations pay for exhibition spots and actively invite end users, creating real business opportunities alongside community building.

The key is finding ways to work with local associations and groups to understand what actually works, not just assuming one approach fits everywhere.

TDT[2]: IXP Initiative helped bridge the gap for new developers by creating pathways for practical experience. How would you extend or modify the IXP model for different regions, ensuring that it aligns with local economic realities and provides value both to developers and companies in various global markets?

Carlos Ospina: That's exactly what the IXP is for; the goal always was to have Colombian companies hiring Colombian IXPs, Brazilian companies hiring Brazilian IXPs, and so on. Today, we have a Colombian company and a Uruguayan company, each with two IXPs.

As I wrote about in "IXP Graduates from Initiative to Program", the program provides 250 contribution credits per successful engagement, but the real value is creating sustainable pathways where companies invest in local talent.

For regional expansion, what we need are local companies that understand their markets. A $5,000 project budget in the US might translate to $2,000 in Colombia while providing equivalent training value. The mentorship and learning outcomes remain the same.

You May Like

Interview

Marcus Johansson's Return to Drupal with AI at Core

Interview

Marcus Johansson's Return to Drupal with AI at Core

The beauty of IXP is that it creates value for everyone. Companies get contribution credits and trained developers, IXPs get paid experience, and the community gets a sustainable talent pipeline. But it only works when companies are actually operating in the local economy, not just international companies with local offices.

TDT[4]: You've pointed out that Drupal's current flat partnership fees don't account for regional economic disparities, making participation harder for organisations in lower-income countries. What alternative models would you propose to make these programs more accessible globally, without compromising the funding that supports the Drupal Association's work?

Carlos Ospina: The model seems to exist. My concern is what is being used to gather feedback about it, how it's promoted, and how we can leverage actual potential partners in each region to validate it.

We need to actually connect with potential partners that work in the local market, not just companies doing work for the same big markets. They have a different perspective and live in a different economic environment.

As I've written about in "Community First, Business Second", we need business sustainability, but not at the expense of excluding entire regions.

What I'd propose is better validation of what's already there. Get real feedback from companies who could benefit but are currently priced out. Understand what pricing works for them versus what revenue the DA needs.

We also need to think about hybrid revenue models. Regional partners could help organise events using approaches that work locally, like the fair-style model I mentioned for DrupalCons, where local businesses pay for exhibition opportunities while creating networking value.

The key is treating this as business development, not charity. Regional partners bring value through local market knowledge, cultural understanding, and cost-effective delivery, benefiting the entire ecosystem.

TDT[4]: You've been vocal about how regional differences impact Drupal's growth. What changes would you propose to ensure that Drupal's community initiatives are designed with enough flexibility to cater to regional needs, while still preserving the integrity of Drupal's core vision and values?

Carlos Ospina: Regional DrupalCons, as I've written about, offer trade and hybrid style models, with a more business-focused approach, while maintaining the community. All this with feedback and support of local associations and groups, we need to listen to other regions.

I've heard several times how people from Africa, LATAM, and other regions feel they are not heard. I think this is cultural, not being ignored on purpose, but we need to understand that the challenges are different and the way to address them may be too.

We need different perspectives based on actual knowledge of regional realities, not just assumptions about what works everywhere.

As I wrote in "The Future of Drupal", we need systematic support that works across different economic and cultural contexts, not just good intentions.

The integrity of Drupal's vision, building great software through an inclusive community, is preserved when we create pathways for authentic regional participation. It's not about compromising standards; it's about recognising that one-size-fits-all approaches often exclude the diversity that makes Drupal stronger.