Drupal AI Contribution meeting 2025-07-14

Some points for the meeting:

1.
Work have been started from @murz / EPAM on a better logging system. The first simple version will supersede AI Logging and use the https://www.drupal.org/project/extended_logger → module to utilize the normal logging system. The AI Logging will be available until 2.0.0 is released, but as soon as this module is available it would be the recomeded module.

The second and more advanced task of the logging will be to create OpenTelemetry logging using another module.

To see discussions and tasks at hand, see: https://www.drupal.org/project/ai/issues/3533109 📌 [Meta] AI Logging/Observability Active

2.
@lussoluca is working on a local development environment, the latest stand is that we are moving it out of the AI module and into its own project as a DDEV plugin. Read more and come with feedback on what you would like to see in the environment here: https://www.drupal.org/project/ai/issues/3532795#comment-16188620 📌 Provide development environment for AI development using DDEV Active

3.
We now have mocking possibilities and AI provider replay possibilities for development and Kernel/Functional testing in the AI Test module. This means that you can record a request once and play it over and over while your are developing or export it into a test.

More information is available in the documentation: https://project.pages.drupalcode.org/ai/1.2.x/developers/virtual_provider/

And in this video: https://www.youtube.com/watch?v=MK6JHmclC-E&ab_channel=DrupalAIVideos

valthebald → credited a.dmitriiev → .

valthebald → credited apmsooner → .

valthebald → credited breidert → .

valthebald → credited dan2k3k4 → .

valthebald → credited kristen pol → .

valthebald → credited matthews → .

valthebald → credited scott_euser → .

valthebald → credited bisonbleu → .

valthebald → credited lussoluca → .

Hi Team & valthebald,

I'd like to share a few thoughts on how we can make our asynchronous meetings more effective and easier to follow.

What I Noticed:

• Topics are not grouped: Items are listed in random order. Grouping them (e.g., Bugs, Features, Design) would make things clearer.
• No clear owners or next steps: It’s not always clear who’s doing what or what should happen after the discussion.
• No meeting summary: There’s no wrap-up message listing key decisions or tasks.
• Too many number emojis in titles: This can make the thread look cluttered and hard to scan.

Suggestions to Improve:

Add a meeting summary at the end:
Include:

• Key topics discussed
• Decisions made
• Action items with names and deadlines
• Any open questions

Group similar topics together:
Use sections like:

• Features / Improvements
• Bugs / Issues
• Tools / Setup
• Ideas

• Assign tasks clearly:

• Use simple tags instead of emojis:

✅ Decision made
❓ Needs more discussion
🔄 Follow-up needed

• Save a copy of the summary:

Thanks
Jaspreet Singh

Looks good, setting this to RTBC.