Tim Doyle, CEO of the Drupal Association with 25 years of experience in the nonprofit sector, dives into the International Drupal Federation Initiative. He discusses the initiative's aim to restructure governance for better global engagement and support for local Drupal associations. The conversation also covers the Modeler API, a tool enhancing communication between developers and business users. Challenges of fostering a united global community and strategies for improving collaboration are explored, highlighting the importance of active involvement from the community.
01:02:56
forum Ask episode
web_stories AI Snips
view_agenda Chapters
auto_awesome Transcript
info_circle Episode notes
insights INSIGHT
Globalizing Drupal Governance
The International Drupal Federation Initiative aims to globalize Drupal governance beyond the US-based Drupal Association.
It seeks shared responsibility for resources like Drupal.org servers and community programs worldwide.
insights INSIGHT
Need for Global Funding and Governance
European open source support is more advanced, prompting Drupal to seek similar international funding.
The federation would improve sustainability and broaden governance inclusivity globally beyond a US-centric model.
insights INSIGHT
Empowering Local Drupal Associations
The federation model will give local Drupal associations formal governance roles.
These associations will elect board members, increasing their influence on Drupal's global direction.
Get the Snipd Podcast app to discover more snips from this episode
In this episode of Talking Drupal, we delve into the International Drupal Federation Initiative with our guest Tim Doyle, CEO of the Drupal Association. We explore the goals, structure, and potential impact of this initiative on the global Drupal community. Additionally, we cover the Modeler API as our module of the week, discussing its functionalities and future potential. Joining the discussion are hosts John Picozzi, Norah Medlin, Nic Laflin, and Martin Anderson-Clutz, who bring their insights and perspectives to the table.
The Modeler API provides an API for modules like ECA - Events, Conditions, Actions, Migrate Visualize, AI Agents, and maybe others. The purpose is to allow those modules to utilize modelers like BPMN.iO, (and maybe others in the future) to build diagrams constructed of their components (e.g. plugins) and write them back into module-specific config entities.
Talking Drupal