Drupal AI Contribution meeting 2025-10-20 (#3553420) · Issues · project / ai

Drupal AI Contribution meeting 2025-10-20

>>> [!note] Migrated issue   Reported by: [valthebald](https://www.drupal.org/user/239562) >>> <p>Drupal AI Contribution meeting from Oct 20, 2025 at 16:00 UTC to Oct 21, 2025 16:00 UTC (Check your local time at <a href="https://www.timebie.com/std/universal.php?q=16">https://www.timebie.com/std/universal.php?q=16</a>)</p> <p>Previous meeting <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3549674" title="Status: Closed (fixed)">#3549674: Drupal AI Contribution meeting 2025-10-06</a></span><br> Next meeting <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai/-/work_items/3554412" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai/-/work_items/3554412</a></span></p> <h2>Where</h2> <p>#ai-contrib channel in <a href="https://www.drupal.org/slack/">Drupal Slack</a></p> <h2>Agenda</h2> <h3>Attendees self-intro and interests</h3> <h3>Follow-up to topics of previous meeting</h3> <h3>Suggest your topic in comments</h3> <h3>Add the issue you want to discuss as a related issue to this meeting</h3> <h2>Transcript</h2> <p>Hello everyone, and welcome to the Drupal AI contribution meeting!<br> This meeting:<br> ➤ Happens every Monday in #ai-contrib channel<br> ➤ Starts at 16:00 UTC (check your time at <a href="https://www.timebie.com/std/universal.php?q=16">https://www.timebie.com/std/universal.php?q=16</a>)<br> ➤ Is text only!<br> ➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously.<br> ➤ New topics are posted at least 5 minutes after previous, to give attendees time to respond/suggest their (sub) topics<br> ➤ Refers to various issues and plans tracking in d.o project: <a href="https://www.drupal.org/project/ai/issues/3553420">https://www.drupal.org/project/ai/issues/3553420</a> Please comment there so we can grant you credit for attending/contributing! Please note, we will only give attributions for active engagement.<br> ➤ Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.<br> Some other emojis used in this meeting:<br> :construction: - issue is in the works<br> :blob_help: - help needed<br> :status_needs_review: - needs review<br> :pear: - low hanging fruit (novice or easy success issue)<br> :comment: - call for discussion</p> <h2>0️⃣ Roll call! Who's here? Please mention your <a href="http://drupal.org">drupal.org</a> username. If you attended DrupalCon Vienna last week, how was your way home? Managed to avoid a Drupal flu?If you haven't, really hope to meet you in person on another occasion! (edited) </h2> <table> <tr> <td>Zoocha Will</td> <td>Hi - @Zoocha WillAt DC Vienna :white_check_mark:Home safely :white_check_mark:Drupal Flu :white_check_mark:</td> </tr> <tr> <td>matthews</td> <td>:wave: MatthewS here. The :airplane: home could have been better - 12 hours of having someone old enough to know better kicking the back of my seat and grumbling about the available space. That said, home and happy. No DrupalFlu - but I am quite tired.</td> </tr> <tr> <td>Dunx</td> <td>dunx - Had a great time in Vienna and nice to meet a heap of the other members of the AI Initiative and others. I seem to have survived any non-self-inflicted illness.</td> </tr> <tr> <td>Gurwinder</td> <td>gantal - Didn't make it to DC Vienna, missed all the fun :disappointed:</td> </tr> <tr> <td>bryan</td> <td>:wave: b_sharpe - I didn't make it but my team said it was awesome</td> </tr> <tr> <td>Arisha Khan</td> <td>arisha here. Couldn't make it to DrupalCon :disappointed:</td> </tr> <tr> <td>dan2k3k4</td> <td>:wave: dan2k3k4Only a ~30min delay at the gate due to plane taking longer to be cleaned up prior boarding, but otherwise all good. Did not get sick.</td> </tr> <tr> <td>Nick Opris</td> <td>:wave: unqunq  For personal reasons I could not attend the DrupalCon in Vienna. Look forward to watching the recordings. (edited)</td> </tr> <tr> <td>valthebald</td> <td>I got my portion of DrupalFlu on the way home, but meeting in person @d34dman, @gxleano, @Marcus Johansson, @yautja_cetanu (Jamie), @Kristen Pol (she/her) , @wouters_f, @dan2k3k4, @artem, @matthews, @breidert, @pdjohnson, @svendecabooter, @Jasper Lammens (sorry if I missed anyone! The last week was packed with the meetings, long and short) was totally worth it! (edited)</td> </tr> <tr> <td>williamsowen</td> <td>williamsowen here! Unfortunately couldn’t make Vienna, but looking forward to watching the sessions! :raised_hands::skin-tone-3:</td> </tr> <tr> <td>Bisonbleu</td> <td>Hello all :wave:, !DCV, !:microbe: I know, lame…</td> </tr> <tr> <td>d34dman</td> <td>Day 3 of DrupalFlu :) one of the most engaging Drupalcon for me. Was able connect with many moving in same direction, so let’s row together :) am so disoriented today that I wrote to somebody  that I would be dead in 2 days. So I would just be silent listener today.</td> </tr> <tr> <td>Marcus Johansson</td> <td>marcus_johansson here - still didn't get it. But its just a matter of time..</td> </tr> <tr> <td>Tyler Staples</td> <td>nexusnovaz - I went! - I got DCFlu - Flight was delayed an hour! - Made it home in one piece!</td> </tr> <tr> <td>littlepixiez</td> <td>Hellooo... littlepixiez here... forgot it was Monday. Sadly didn't go to DC Vienna :cry:  Butt... hope to see you next time!</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>Kristen, California :wave:Was in ViennaNo Drupal flu yet but I got home 36 hours ago so we’ll see It was a good event (ignoring the conference food)Spent too much of it in my apartment working on my talks so that part wasn’t great Hope to see people in Chicago</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>I do have jet lag though… didn’t sleep well last night :scream:</td> </tr> <tr> <td>pdjohnson</td> <td>@valthebald echo that. Nice to meet you. Was a busy week indeed between meetings, looking after clients, talking Drupal AI and marketing, taking photos. I love the buzz of DrupalCon. Sorry to hear you are ill.</td> </tr> <tr> <td>Titi Dumitrescu</td> <td>oldspot on <a href="http://d.org">d.org</a> - yes i attended DC Vienna and it was an amazing event. luckily i managed to get away without the DCFlu !</td> </tr> </table> <h2>1️⃣ Release announcements/schedule</h2> <table> </table> <h2>1️⃣ 1️⃣ Version 1.2.0 (quickly followed by <a href="https://www.drupal.org/project/ai/releases/1.2.1">1.2.1</a>) is out!</h2> <table> <tr> <td>valthebald</td> <td>Best release so far IMO (and let's hope this continues to be the case with the future releases) :tada:</td> </tr> <tr> <td>valthebald</td> <td>Release was out-shadowed by Driesnote and many great talks that happened in Vienna, but I believe it is a big deal</td> </tr> <tr> <td>valthebald</td> <td>From 1.0 to 1.1, and then from 1.1 to 1.2, more and more people (you included) contribute to the ecosystem</td> </tr> <tr> <td>matthews</td> <td>It is a huge deal. Very proud of our international cadre of AI-ers.</td> </tr> <tr> <td>valthebald</td> <td>so it's not anymore what can be seen as a side project of a single person or a company, but a joint effort of many</td> </tr> <tr> <td>Marcus Johansson</td> <td>Just to reiterate @valthebald point - 127 different contributors from 64 organizations did contribute to 1.2.0 in one way or another.</td> </tr> </table> <h2>1️⃣ 2️⃣ 2.0 becomes default branch for all open issues</h2> <table> <tr> <td>valthebald</td> <td>2.0.x is already marked as default branch for all new issues, and we will go over and switch most of open issues to this version as well</td> </tr> <tr> <td>valthebald</td> <td>since forward-porting has proven to be no the best flow</td> </tr> <tr> <td>valthebald</td> <td>The goal is to have 2.0.0 by early January 2026, and ship it as part of Drupal CMS 2.0</td> </tr> </table> <h2>1️⃣ 3️⃣ 1.3 becomes a "plan B" path</h2> <table> <tr> <td>valthebald</td> <td>In case there are features that are low-hanging fruits, but are not strictly backwards-compatible, there will be an interim 1.3.x branch</td> </tr> <tr> <td>valthebald</td> <td>Also, if we see that refactored release 2.0.0 is impossible by January, Drupal CMS 2.0 will ship with 1.3.0</td> </tr> <tr> <td>matthews</td> <td>When will we have the cutoff date for Drupal CMS 2.0?</td> </tr> <tr> <td>valthebald</td> <td>@Kristen Pol (she/her) that's probably the question for you ^</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>I’ll check</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>I pinged the CMS team and @pameeela is wondering what specifically do we have in mind for Drupal CMS 2.0?I know we want to figure out how to include ai_context but I’m unclear on other thingsNote there is a way to add optional recipes at any time so that will be good for immediate impact recipes cc @Marcus Johansson @yautja_cetanu (Jamie) @breidert</td> </tr> <tr> <td>yautja_cetanu (Jamie)</td> <td>We're discussing things with Dries early November to decide.I really wanna get on the meta schema stuff if we can have Ahmed ahkil push that forward. We really want to get MCP by Drupal CMS. We think a really simple recipe that provide read only MCP access to public content types. Someone was working on that in the contrib day (didnt get his name) and almost finished a recipe with that but Adam was going to help him with the final part.I think it would be good to get flowdrop and tools API which would allow us to have agents that actually create and edit content too, as well as categorize them.</td> </tr> <tr> <td>Marcus Johansson</td> <td>I think we should add some recipes for FWA as well. The current agent system can do the agents as well, if Flowdrop is not ready by then.</td> </tr> <tr> <td>yautja_cetanu (Jamie)</td> <td>Yup!</td> </tr> <tr> <td>breidert</td> <td>Sorry for replying late - I am suffering Drupalflu - I think recipes, testing, and UX would be nice to have in DCMS 2.0</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>Meeting #3 noted here would be a good place to discuss these with Pam+Lauri et al<a href="https://drupal.slack.com/archives/C08QK2N7PMM/p1761169122446759?thread_ts=1760974024.351449&channel=C08QK2N7PMM&message_ts=1761169122.446759">https://drupal.slack.com/archives/C08QK2N7PMM/p1761169122446759?thread_ts=1760974024.351449&channel=C08QK2N7PMM&message_ts=1761169122.446759</a></td> </tr> </table> <h2>2️⃣ DrupalCon Vienna retrospective</h2> <table> </table> <h2>2️⃣ 1️⃣ AI-related sessions</h2> <table> <tr> <td>valthebald</td> <td>AI was clearly one of the DrupalCon hot topics, with too many sessions having it in agenda. Which ones did you attend and would recommend?</td> </tr> <tr> <td>valthebald</td> <td>Videos should appear on YouTube after some delay, so hopefully we will be able to post the links in one of the following meetings</td> </tr> <tr> <td>matthews</td> <td><a href="https://events.drupal.org/vienna2025/session/post-product-product-manifesto-ai-disrupting-both-saas-and-consulting-world-how">The post-product product manifesto: AI is disrupting both the SaaS and the consulting world, how to turn this threat into a Drupal renaissance</a><a href="https://events.drupal.org/vienna2025/session/ai-agent-swarm-has-come-drupal-canvashttps://events.drupal.org/vienna2025/session/migrating-anything-and-everything-drupal-canvashttps://events.drupal.org/vienna2025/session/drupal-ai-strategy-and-application">https://events.drupal.org/vienna2025/session/ai-agent-swarm-has-come-drupal-canvashttps://events.drupal.org/vienna2025/session/migrating-anything-and-everything-drupal-canvashttps://events.drupal.org/vienna2025/session/drupal-ai-strategy-and-application</a></td> </tr> <tr> <td>Dunx</td> <td>Just about every talk involved AI, but I actually wanted to see more on Canvas and site templates, so prioritised those as I'm more up-to-speed with the latest on AI. I'll catch up when they're released for the inevitable sessions I missed or had clashes for.</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>See als[#3552852]</td> </tr> </table> <h2>2️⃣ 2️⃣ Scope for AI 2.0 becomes clearer</h2> <table> <tr> <td>valthebald</td> <td>Do not expect too many ground-breaking (feature-wise) changes in 2.0!</td> </tr> <tr> <td>valthebald</td> <td>Change in the major version reflects the long-awaited need to refactor things that existed in pre-1.0 (only one year ago! think about it) and were never revisited</td> </tr> <tr> <td>valthebald</td> <td>now that we have AI module tested not only by early adopters, but also finding its way into production sites, it's time to rethink some architectural decisions</td> </tr> </table> <h2>2️⃣ 3️⃣ <a href="https://www.drupal.org/project/issues/search/ai?text=&assigned=&submitted=&project_issue_followers=&status%5B%5D=Open&issue_tags_op=%3D&issue_tags=priority">Priority issues for AI 2.0</a></h2> <table> <tr> <td>valthebald</td> <td>you may notice, that there are many "move module X out of the core" issues</td> </tr> <tr> <td>valthebald</td> <td>Moving submodules out of the core will allow them to move at a different pace, but may also require more dedication from maintainers.</td> </tr> <tr> <td>valthebald</td> <td>If you feel like joining any of the submodules' team, please write the current maintainer(s) or here</td> </tr> <tr> <td>valthebald</td> <td>If you see @Marcus Johansson as the only maintainer for a given module, that probably means he'd be glad to share this responsibility (but he'll know better of course)</td> </tr> <tr> <td>matthews</td> <td>@valthebald It might also help to pull the list of submodules being pulled in a separate document from the issue queue.</td> </tr> <tr> <td>valthebald</td> <td>@matthews good point! I'll add this to my todo list</td> </tr> <tr> <td>valthebald</td> <td>One of the concerns raised during the discussion of this "big move" was even bigger segmentation and the need to assemble a site from too many components, but from the other side, having AI recipe (or recipes) in CMS 2.0 would help a lot</td> </tr> <tr> <td>matthews</td> <td>I'm worried about some of these modules "getting left behind". But on the other hand, we don't want less important issues keeping a new version from getting released.</td> </tr> <tr> <td>valthebald</td> <td>this will probably be a "try and see" process</td> </tr> <tr> <td>valthebald</td> <td>we'll find out soon 🙂</td> </tr> <tr> <td>Marcus Johansson</td> <td>@matthews - I think the opposite might happen with the modules that people actually maintain. Currently they are stuck in limbo waiting for a 3 months release cycle to be released, even if they could have had 2-3 minor versions released in between.So it makes the release management for AI core better at the same time as it makes the maintainers of the moved out submodules less frustrated to have to wait for release windows.AI Logging might be the one, where it doesn't get any love, because no one wants to maintain it, but that was true while it was in the AI as a submodule as well. The AI Observability has a clear and commited maintainer in @Alexey Murz Korepov which is nice</td> </tr> <tr> <td>matthews</td> <td>@Marcus Johansson I think the decisions were good ones, to be clear.</td> </tr> </table> <h2>3️⃣ Open Mike! What are you working on? Are you blocked? Or do you want to discuss a specific topic? Add your status, questions, and topics (and discuss them in threads) for another 23 hours. Start with a number like 3️⃣ 1️⃣, 3️⃣ 2️⃣ etc.It is also ok to add sub-items to previous items - those will be published in the correct order in the meeting transcript</h2> <table> <tr> <td>matthews</td> <td>3️⃣ 1️⃣ I'm giving a full day training at NEDCamp in November. I'm reworking the curriculum (it was originally created for GovCon) a little bit based on what I learned this past week. I think NEDCamp will probably be my last event for the year - but this year was a DOOZY.Florida DrupalcampDrupalcon AtlantaDrupalcamp AshevilleDrupalcamp ColoradoMIDCampGovConBADCampDrupalcon ViennaNEDCampPlus I spoke for GAAD at the University of Denver and numerous webinars.I'm grateful to the entire community for one HECK of a year. (edited)</td> </tr> <tr> <td>wouters_f</td> <td>I’m working on <a href="https://www.drupal.org/project/ai_consoleA">https://www.drupal.org/project/ai_consoleA</a> admin console that you can use to interact with your agentsIn games it is a standard to open the console with a certain key. and you know without thinking what you get there.I think we should have the same standard in open source systemsOpen the console to have your personal admin ai assistant.</td> </tr> <tr> <td>Bisonbleu</td> <td>I could use :eyes: on these issues i.e. looking for reviews: the 1st one is about the Tools Explorer form and is low-compute, the 2nd one is about ai_agents_test  and is medium compute[#3541323]</td> </tr> <tr> <td>Zoocha Will</td> <td>I am working on a doc for attracting new ‘end user’ organization makers with Dominique</td> </tr> <tr> <td>Nick Opris</td> <td>We need this reviewed and merged when someone has a few minutes to test.<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai_agents/-/work_items/3535760" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai_agents/-/work_items/3535760</a></span></td> </tr> <tr> <td>Nick Opris</td> <td>Also this one takes a minute[#3552641]</td> </tr> <tr> <td>Dunx</td> <td>I've asked my team to look at the above 4 tickets that need review.</td> </tr> </table> <h2>3️⃣1️⃣ Moving submodules out of AI Core</h2> <table> <tr> <td>artem</td> <td>it was found out, that all submodules already have a packagist namespace</td> </tr> <tr> <td>artem</td> <td>for example for submodule field_widget_actions there is already drupal/field_widget_actions namespace</td> </tr> <tr> <td>artem</td> <td>so for the newly created <a href="https://www.drupal.org/project/field_widget_actions">https://www.drupal.org/project/field_widget_actions</a> the namespace is ‘drupal/field_widget_actions-field_widget_actions’</td> </tr> <tr> <td>artem</td> <td>and it will be like that for all other submodules that are going out to become standalone projects</td> </tr> <tr> <td>artem</td> <td>in #contribute channel it was recommended to create an issue in this project <a href="https://www.drupal.org/project/project_composer/">https://www.drupal.org/project/project_composer/</a></td> </tr> <tr> <td>artem</td> <td>here is the one for field_widget_actions[#3553545]</td> </tr> <tr> <td>artem</td> <td>it seems that all other submodules will have the same problem, so they will all need the same actions</td> </tr> <tr> <td>valthebald</td> <td>for ai_translate, we're going to use existing drupal/ai_translate namespace</td> </tr> <tr> <td>valthebald</td> <td>@artem and I see that you're maintainer of field_widget_actions</td> </tr> <tr> <td>valthebald</td> <td>why would you need a new namespace?</td> </tr> <tr> <td>artem</td> <td>because drupal packagist has already created a composer namespace for all submodules</td> </tr> <tr> <td>artem</td> <td>the namespace not for drupal project and not for gitlab, but for composer</td> </tr> <tr> <td>artem</td> <td>you were lucky to have your namespace before the module was merged to AI Core as a submodule</td> </tr> <tr> <td>artem</td> <td>but all submodules that were created only inside AI core will have the same problem as with field widget actions</td> </tr> <tr> <td>valthebald</td> <td>you mean, drupal packagist will pull drupal/field_widget_action from ai/modules/field_widget_action rather than from field_widget_action?</td> </tr> <tr> <td>artem</td> <td>exactly</td> </tr> <tr> <td>valthebald</td> <td>it's already happened that namespaces moved from and into the core, should it be different for a contrib module?</td> </tr> <tr> <td>artem</td> <td>the core maintainers probably have more influence on packagist 🙂</td> </tr> <tr> <td>artem</td> <td>I have created an issue, maybe they did it silently, as they know who should do this</td> </tr> <tr> <td>valthebald</td> <td>I will add other modules to the same issue (ai_translate is affected too :disappointed: ), so that all of them can be handled at once</td> </tr> </table> <h2>3️⃣ 2️⃣ Prioritizing Dries UX feedback[#3552811]</h2> <table> <tr> <td>Kristen Pol (she/her)</td> <td>We should have a dedicated meeting for this IMO We can also consider discussing this as part of the weekly UX meeting once I’ve rescheduled so I can attend cc @Marcus Johansson @breidert @yautja_cetanu (Jamie) @Emma Horrell @Aidan Foster @ckrina</td> </tr> <tr> <td>Marcus Johansson</td> <td>Yes, this would be great. I will try to attend the UX meetings from now on as well, just to listen in - could someone send me an invite to those. I think we need to focus on the agents form, if there is capacity for UX/UI to help out with this as well.</td> </tr> <tr> <td>breidert</td> <td>Hello folks, the following is happening with UX:Meetings with the UX + frontenders from 1x with Emma and Christina have taken place. As a result we concluded, that the first step is to create a user journey map, to adress pain points in important journes. You can follow the work in <a href="https://www.figma.com/board/PNL46ECSSiZFowQMLDHxky/Drupal-AI-UX-Briefing?node-id=2-3&t=1AYXYDR9ZpTlCWTw-1">this Figma</a>.The main point identified is that people don't know which configuration is where. There exists a proposal to create a dashboard with checklists to guide users. The coresponding issue will be fleshed out this week, so we can review and then implement it.The detail screens will be adressed next, as soon as we have navigation out of the wayAll work will be aligned with Drupal CMS, as we want to have the same UX patterns for both, and also we want to use Drupal CMS as product displayBesides 1x Zoocha will also provide UX resourcesThe Monday-Meeting will likely change, as the focus changes from an alignment meeting to a implementation meeting. I think it will take 1-2 weeks until the UX work can start to take effect and it will be worthwile to join this meeting to get first-hand information.</td> </tr> <tr> <td>Kristen Pol (she/her)</td> <td>@Marcus Johansson I’ve added you to the existing meeting for now but it sounds like Christoph doesn’t think you need to be there just yetPerhaps ping him before attending or pop on and see if you are needed</td> </tr> </table> <h2>3️⃣ 3️⃣ If you were contributing to or speaking about Drupal AI at DrupalCon Vienna and aren’t listed already, add a comment on this issue with your name and what you were focused o[#3552920]</h2> <table> </table> <p>Participants:</p> <p>Zoocha Will, matthews, Dunx, Gurwinder, bryan, Arisha Khan, dan2k3k4, Nick Opris, valthebald, williamsowen, Bisonbleu, d34dman, Marcus Johansson, Tyler Staples, littlepixiez, Kristen Pol, pdjohnson, Titi Dumitrescu, wouters_f</p>

issue