Category: News
Talking Drupal: Talking Drupal #485 – AI Autonomy
Today we are talking about AI Autonomy, How it could help Drupal Development, and AI in the future with guest Jay Callicott. We’ll also cover AI Agents as our module of the week.
For show notes visit: https://www.talkingDrupal.com/485
Topics
- What got you interested in this topic
- What is meant by AI Autonomy
- You suggested in your blog post in the Drop Times that developers will manage AI can you elaborate
- AI coming for our jobs
- Drupal X
- Do decoupled sites have an advantage
- Is the future going to be all prompts
- Skill decay
- What would you say to a CEO thinking about replacing developers with AI
Resources
- Drupal is Great! Its Perception Might Not Be.
- The AI-Driven Developer: From Assistance to Autonomy in Drupal Development
- DrupalX
- Ethics of AI
Guests
Jay Callicott – drupalninja99
Hosts
Nic Laflin – nLighteneddevelopment.com nicxvan John Picozzi – epam.com johnpicozzi Scott Weston – scott-weston
MOTW Correspondent
Martin Anderson-Clutz – mandclu.com mandclu
- Brief description:
- Have you ever wanted to leverage AI-powered tools to get information about or change the configuration of your website? There’s a module for that
- Module name/project name:
- Brief history
- How old: created in Aug 2024 by Marcus Johansson (marcus_johansson) of FreelyGive
- Versions available: 1.0.1 which supports Drupal 10.3 and 11
- Maintainership
- Actively maintained: that release was in the past week, and was part of the significant effort to get stable releases of the AI modules that are included in Drupal CMS
- Security coverage
- Documentation included within the module’s codebase
- Number of open issues: 30 open issues, 7 of which are bugs against the current branch
- Usage stats:
- 119 sites but I suspect that number will increase rapidly once people start using Drupal CMS
- Module features and usage
- In AI terminology, an agent is a system able to interact with its environment, collect data, and use the data to perform self-determined tasks
- The AI Agents module is a framework to provide agents that can perform a variety of functions in your Drupal website
- It depends on the AI module that we had Jamie Abrahams on the podcast to talk about back in episode #468
- The module includes plugins that provide three agents, namely:
- A Field Type Agent that can create or edit fields using the Field API, or answer questions about the fields your site has defined
- A Content Type agent that can create, edit, or answer questions about node types
- Taxonomy Agent that can do the same for your site’s vocabularies
- Anyone who saw the Driesnote AI demos from DrupalCon Barcelona or Singapore will have seen agents in action, in that example through interaction in a chatbot
- Technically, the plugins are UI agnostic, however. So theoretically you could trigger an agent in other ways. But today, AI Agents power the AI chatbot that you can use in the AI recipe that is included in the recently released Drupal CMS 1.0
- The AI Agents module also includes some submodules. An experimental form integration submodule adds UI elements to the interfaces for managing fields, content types, and vocabularies, an explorer submodule provides debugging tools, and an experimental Extra submodule provides agents for working with webforms and views. I have also seen a demo of some work underway to provide an ECA agent, so you may soon be able to get your Drupal site to build out ECA models based on the business logic you describe to it
GNU Guix: Meet Guix at FOSDEM
Next week will be FOSDEM time for Guix! As
in previous years, a
sizable delegation of Guix community members will be in Brussels. Right
before FOSDEM, about sixty of us will gather on January 30–31 for
the now traditional Guix Days!
In pure unconference style, we will self-organize and discuss and/or
hack on hot topics: drawing lessons from the user & contributor
survey,
improving the contributor workflow, sustaining our infrastructure,
improving governance and processes, writing the build daemon in Guile,
optimizing guix pull
, Goblinizing the Shepherd… there’s no shortage
of topics!
This time we’ve definitely reached the maximum capacity of our
venue
so please do not just show up if you did not
register. Next
year we’ll have to find a larger venue!
As for FOSDEM itself, here’s your agenda if you want to hear about Guix
and related projects, be it on-line or on-site.
On Saturday, February 1st, in the Open Research
track:
- Guix + Software Heritage: Source Code Archiving to the Rescue of
Reproducible
Deployment,
at noon, where Simon Tournier will talk about the latest
developments connecting Guix and the Software Heritage
archive.
On Sunday, February 2nd, do not miss the amazing Declarative &
Minimalistic Computing
track! It will
feature many Guile- and Guix-adjacent talks, in particular:
- RDE: Tools for managing reproducible development
environments,
where Nicolas Grave will present how RDE extends Guix and what nifty
features it brings; - The Shepherd: Minimalism in
PID 1,
where I (Ludovic Courtès) will talk about the recently-released
Shepherd 1.0
and why I think its design makes it the coolest init system to hack
on; - Shepherd with Spritely Goblins for Secure System Layer
Collaboration,
where Juliana Sims of Spritely will present on-going work to port
the Shepherd to
Goblins
in support of distributed and capability-based secure computing.
But really, there’s a lot more to see in this track, starting with talks
by our Spritely friends on web development with Guile and Hoot by David
Thompson,
a presentation of the Goblins distributed computing framework by
Jessica
Tallon,
and one on Spritely’s vision by Christine Lemmer-Webber
herself
(Spritely will be present in other tracks
too,
check it out!), as well as a talk by Andy Wingo on what may become
Guile’s new garbage
collector.
Good times ahead!
Guix Days graphics are copyright © 2024 Luis Felipe López Acevedo,
under CC-BY-SA 4.0,
available from Luis’ Guix graphics
repository.
9front “THIS TIME DEFINITELY” released
Tennis – Australian Open 2025 – Gaël Monfils : “I’ve given everything, I can’t give more, I’ve…
#! code: Drupal 11: Creating Custom Queues
Creating queues using the core queue classes in Drupal is fairly straightforward. You just need a mechanism of adding data to the queue and a worker to process that data.
As the data you add to the queue is serialised you can add pretty much any data you want to the queue, so the only limitation is rebuilding the data once you pull it out of the queue.
There are some situations where the core Drupal queue system needs to be altered in some way. You might want to separate the data into different tables, or have a different logic for creating or storing the queue items, or even integrate with a third party queue system for manage the queues.
Whilst all of these examples are possible, they require a certain amount of understanding of the queue API and need additional services and settings to get working.
In this article we will look at how to create a custom queue, along with the queue factory needed to integrate that queue with Drupal. We will also look at some settings needed to swap out certain queues for you custom queue implementations. All of the code seen in this article is available in our Drupal Queue Examples repository on GitHub, specifically the queue_custom_example module.
First, let’s look at what is requires for a queue to work in Drupal.
Create A Custom Queue With The QueueInterface Interface
The interface DrupalCoreQueueQueueInterface is used to build the framework of the queue, which is used to manage the queue items. Your queue object must have the following methods.
philipnorton42
Sun, 01/19/2025 – 19:54