Listen in the Podli app 🎧
Follow your favourite podcasts, listen offline and in the car with CarPlay and Android Auto, and always pick up where you left off. Free to try.
Today we are talking about the UN, Open Source, and Drupal with guests Tim Lehnen & Henry Poole. We'll also cover Live Update as our module of the week.
For show notes visit:
https://www.talkingDrupal.com/574
Topics
- What Is UN Open Source Week
- Why Open Source Fits UN Goals
- Who Attends and What Tech Is There
- Conference Audience and DPI DPG
- Drupal as a Digital Public Good
- UN Uses Drupal at Scale
- Why Attend and What to Gain
- Upstream First Contracting
- Open Procurement Curriculum
- Reaching Procurement Conferences
- Steering Spend Upstream
- Funding Open Source Legally
- Talking Louder Beyond Drupal
- Digital Sovereignty Explained
- Governance Values Matter
- Fixing Funding Perception
- Community Next Steps Closing
Resources
Guests
Henry Poole - civicactions.com henry-poole
Tim Lehnen - drupal.org hestenet
Hosts
Nic Laflin - nLighteneddevelopment.com nicxvan
John Picozzi - epam.com johnpicozzi
Tim Sharp - tea-sharp
MOTW Correspondent
Martin Anderson-Clutz - mandclu.com mandclu
- Brief description:
- Have you ever wanted parts of your Drupal pages, like blocks, views, or notifications, to update in real time without a page refresh, and without having to stand up extra infrastructure to do it? There's a module for that.
- Module name/project name:
- Brief history
- How old: created in Sep 2026 by Alessandro Feijó (afeijo) of Mindcore
- Versions available: 1.0.0-alpha6, which works with Drupal 11 and 12
- Maintainership
- Actively maintained, latest release just a week ago
- No security coverage yet, since it was just created and only has alpha releases
- Test coverage
- Documentation: a detailed README, plus a roadmap doc and a built-in demo page
- Number of open issues: none
- Usage stats:
- Module features and usage
- Live Update positions itself as a generic real-time event layer for Drupal: modules publish events to named channels, and browsers subscribed to those channels update just the affected part of the page
- Out of the box it uses plain HTTP polling back to Drupal, every 5 seconds by default, so it works on pretty much any host with no extra