Drupal AI Contribution meeting 2025-08-18
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3541345. -->
Reported by: [valthebald](https://www.drupal.org/user/239562)
>>>
<p>Drupal AI Contribution meeting from Aug 18, 2025 at 16:00 UTC to Aug 19, 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/3540027" title="Status: Closed (fixed)">#3540027: Drupal AI Contribution meeting 2025-08-11</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/3542355" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai/-/work_items/3542355</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>AI recipes marketplace</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: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3541345" title="Status: Closed (fixed)">#3541345: Drupal AI Contribution meeting 2025-08-18</a></span> 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.</p>
<h2>0️⃣ Roll call! Who's here? Please mention your d.o. username. With DrupalCon Vienna approaching (too) fast, what features would you like to see in AI module by the start of it? (edited) </h2>
<table>
<tr>
<td>robertoperuzzo</td>
<td>robertoperuzzo :wave:</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>nikro :eyes:</td>
</tr>
<tr>
<td>Dunx</td>
<td>dunx :wave:AI is moving so fat (generally) that clients are struggling to engage. We're concentrating on demos for functionality that already exists, so that sort of thing is high on my want list. Already good sources are:<a href="https://workflows-of-ai.com/https://www.ai4drupal.org/">https://workflows-of-ai.com/https://www.ai4drupal.org/</a> (coming soon I think)</td>
</tr>
<tr>
<td>Dunx</td>
<td>fat = 'fast' :laughing:</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Hi all, :wave: Renaud here in Montreal… What features do I want before DrupalCon Vienna, October 14 to 17, 2025? Honestly, that’s a tough call… :thinking_face:</td>
</tr>
<tr>
<td>thejimbirch</td>
<td>thejimbirch :wave:</td>
</tr>
<tr>
<td>Tyler Staples</td>
<td>nexusnovazSome way of seeing what the agent would do in a flow graph of some kind (if im understanding the project correctly, something exactly like React Flow in 3.4)</td>
</tr>
<tr>
<td>bryan</td>
<td>b_sharpe :wave:</td>
</tr>
<tr>
<td>Gábor Hojtsy (he/him)</td>
<td>Vienna is going to be epic! I created this video to promote the AI makers content: <a href="https://www.linkedin.com/posts/ghojtsy_with-the-recent-announcement-of-the-drupal-activity-7362173410522673152-pTcq?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAt5mYABzo9cvzkEPxaRjGSuWLqM4aY0b-g">https://www.linkedin.com/posts/ghojtsy_with-the-recent-announcement-of-the-drupal-act[…]m=member_desktop&rcm=ACoAAAt5mYABzo9cvzkEPxaRjGSuWLqM4aY0b-g</a> 🙂For what would be great to see, for me it would be MCP support in Drupal CMS, maybe with a nice demo of how the target audience would use it for a specific task. I really liked @Giorgi Jibladze's recent MCP release demo 🙂</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Kristen, California :wave: I'm most excited about the XB and design system AI features but I'm most familiar with that space these days</td>
</tr>
<tr>
<td>beautifulmind</td>
<td>beautifulmind :wave:It's exciting to see the progress of the Drupal AI initiative and the fascinating development work that's happening.</td>
</tr>
<tr>
<td>matthews</td>
<td>MatthewS, Colorado.</td>
</tr>
<tr>
<td>the_g_bomb</td>
<td>Gareth - the_g_bomb. Would love to see contextual alt text generation, but there are lots of issues to solve first, so not holding my breath</td>
</tr>
<tr>
<td>dan2k3k4</td>
<td>dan2k3k4 :wave:</td>
</tr>
<tr>
<td>d34dman</td>
<td>Shibin Das (d34dman) hi 🙂</td>
</tr>
</table>
<h2>1️⃣ Follow-up from the last week</h2>
<table>
<tr>
<td>robertoperuzzo</td>
<td>Last week I was off.Following what I wrote here [2. DDEV Drupal AI Add-on]<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3532795" title="Status: Closed (fixed)">#3532795: Provide development environment for AI development using DDEV</a></span>#comment-16218979), today I created the new [pgvector DDEV add-on](<a href="https://github.com/robertoperuzzo/ddev-pgvector">https://github.com/robertoperuzzo/ddev-pgvector</a>) and now I'm working on a raw version of the [drupal-ai DDEV addon](<a href="https://github.com/Drupal-AI/ddev-drupal-ai/tree/1-implement-the-cli-commands">https://github.com/Drupal-AI/ddev-drupal-ai/tree/1-implement-the-cli-commands</a>).</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>React Flow UI - assembled few elements - mostly inspiring from LangFlow -<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/react_flow/issues/3537374" title="Status: Active">#3537374: React Flow UI Work</a></span></td>
</tr>
<tr>
<td>robertoperuzzo</td>
<td>Here is a quick demo of the wizard setup. But this is only a rough starting point for discussion</td>
</tr>
<tr>
<td>Tyler Staples</td>
<td>I really like that little demo for the ddev addon. I've had to go and set it all up manually, and although it wasn't a long process, its some bits just make it a little easier.</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Nice wizard :heart_eyes:</td>
</tr>
<tr>
<td>beautifulmind</td>
<td>That's fantastic! :clap:</td>
</tr>
<tr>
<td>matthews</td>
<td>:mage:</td>
</tr>
</table>
<h2>1️⃣ 1️⃣ Releases in 1.2.x and 1.1.x</h2>
<table>
<tr>
<td>valthebald</td>
<td>1.2.0 alpha 2 <a href="https://www.drupal.org/project/ai/releases/1.2.0-alpha2">https://www.drupal.org/project/ai/releases/1.2.0-alpha2</a></td>
</tr>
<tr>
<td>valthebald</td>
<td>and 1.1.3 <a href="https://www.drupal.org/project/ai/releases/1.1.3">https://www.drupal.org/project/ai/releases/1.1.3</a></td>
</tr>
<tr>
<td>valthebald</td>
<td>are out. No releases are planned this week</td>
</tr>
</table>
<h2>2️⃣ Priority areas for this week</h2>
<table>
</table>
<h2>2️⃣ 1️⃣ Base tools :construction:</h2>
<table>
<tr>
<td>valthebald</td>
<td><a href="https://www.drupal.org/node/3528974">https://www.drupal.org/node/3528974</a> waits for the feedback</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>@michaellander is working on this</td>
</tr>
</table>
<h2>2️⃣ 2️⃣ Tools in streamed chats :construction:</h2>
<table>
<tr>
<td>valthebald</td>
<td><a href="https://www.drupal.org/project/ai/issues/3528549">https://www.drupal.org/project/ai/issues/3528549</a></td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>assigned to Marcus</td>
</tr>
</table>
<h2>2️⃣ 3️⃣ Fibers for cooperative performance gain</h2>
<table>
<tr>
<td>valthebald</td>
<td><a href="https://www.drupal.org/project/ai/issues/3538027">https://www.drupal.org/project/ai/issues/3538027</a></td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>assigned to @Andrew Belcher</td>
</tr>
</table>
<h2>2️⃣ 4️⃣ Guardrails and security :construction: (edited) </h2>
<table>
<tr>
<td>valthebald</td>
<td><a href="https://www.drupal.org/project/ai/issues/3518963">https://www.drupal.org/project/ai/issues/3518963</a></td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>assigned to @lussoluca</td>
</tr>
</table>
<h2>2️⃣ 5️⃣ Multiple automators per field UI/UX</h2>
<table>
<tr>
<td>valthebald</td>
<td><a href="https://www.drupal.org/project/ai/issues/3535824">https://www.drupal.org/project/ai/issues/3535824</a></td>
</tr>
<tr>
<td>Dunx</td>
<td>Latest suggestion seems very sensible and feedback sought.</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>assigned to @bryan</td>
</tr>
</table>
<h2>3️⃣ Can we do an async agile stand-up?</h2>
<table>
</table>
<h2>Start a thread with 3️⃣ 1️⃣ , 3️⃣ 2️⃣ etc, describing what are you working on, want to discuss, need a review, or/and are blocked?</h2>
<table>
</table>
<h2>3️⃣ 1️⃣ AI issue tracker</h2>
<table>
<tr>
<td>valthebald</td>
<td>I will go on and suggest a first topic 🙂</td>
</tr>
<tr>
<td>valthebald</td>
<td>Jamie has created a meta issue[#3538456]</td>
</tr>
<tr>
<td>valthebald</td>
<td>My plan for this week is to review claude-generated code and fixed already known issues</td>
</tr>
<tr>
<td>valthebald</td>
<td>no feedback needed at this point</td>
</tr>
</table>
<h2>3️⃣ 2️⃣ <a href="https://www.drupal.org/project/ai_initiative/issues/3538378">[Meta] SEO Track for the Drupal AI Initiative</a> - Still seeking input of what AI SEO features folks want. We are waiting for the survey results, then will start formulating a plan.</h2>
<table>
<tr>
<td>Kristen Pol (she/her)</td>
<td>@breidert do you think Jim could get a sneak peak at results so he's unblocked from that side of things?</td>
</tr>
<tr>
<td>breidert</td>
<td>Hello @thejimbirch - SEO was ranked the 7th most important AI feature for Drupal (out of 34) in the survey (216 AI professionals, business leaders, and technical decision makers from 199 organizations). The main points respondents raised about SEO were:Positive Feedback:SEO Optimizer seen as highly beneficial, automating tasks like generating structured data (JSON-LD) and auditing for best practices.Potential for time-saving for developers and content teams.Integration with existing SEO modules and multilingual schema support desired.Could enhance content discoverability for search engines and AI systems.Suggestions for features like title suggestions and auto-tagging.Importance for API and MCP server connections highlighted.Critical Feedback:Skepticism about traditional SEO's continued relevance.AI for SEO might be unnecessary if data is well-structured.Concerns that search engines could perform SEO optimization more effectively.Sentiment that SEO is becoming a "zero-sum game."Traditional SEO and manual metadata becoming less crucial.Content quality, user behavior, and semantic relevance prioritized by AI and search engines.(edited)</td>
</tr>
<tr>
<td>breidert</td>
<td>IMO this is valueable feedback. It shows both what users want, but also points you to potential difficulties.</td>
</tr>
<tr>
<td>breidert</td>
<td>It's not direct guidelines how to build the perfect feature, but it provides guidance what functionality to build first and where to be careful.</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Thanks so much :pray:</td>
</tr>
<tr>
<td>thejimbirch</td>
<td>Thanks @breidert. I added it to the issue and will start working on a functionality scope plan.</td>
</tr>
</table>
<h2>3️⃣ . 3️⃣ Selling it to clients</h2>
<table>
<tr>
<td>Dunx</td>
<td>As per my intro, it's all about demos for us. For many clients, AI seems magical and so must cost a lot to implement. Showing them how easy it is to create these features is a must. We're toying with the idea of some t-shirt sizing for features.</td>
</tr>
<tr>
<td>valthebald</td>
<td>I reckon @Seogow has started some similar effort last week</td>
</tr>
<tr>
<td>valthebald</td>
<td><a href="https://www.ai4drupal.org/">https://www.ai4drupal.org/</a></td>
</tr>
<tr>
<td>Dunx</td>
<td>Yup. Looking forward to how that pans out.</td>
</tr>
<tr>
<td>Seogow</td>
<td>@Dunx I have pretty good plan (I think) how to show all the killer AI functionality. Unfortunately, since I am out of the job, almost all my efforts are pointed to paying bills. I hope to land something soon, ideally in Drupal, so I could speed-up.</td>
</tr>
<tr>
<td>Dunx</td>
<td>That's not good to hear. Site would be great for your Drupal CV :wink: . Good luck with the search.</td>
</tr>
<tr>
<td>Seogow</td>
<td>@Dunx thanks!</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>I can't go into details yet but there will be an official AI demo page coming out "soon" (I assume within the next few weeks)This doesn't discount the usefulness of other demos for the community and end usersDrupal Forge is a great place for demos and there is lots of room for the community to demo far and wide to get as many eyes as possible</td>
</tr>
<tr>
<td>Seogow</td>
<td>@Kristen Pol (she/her) Thanks for letting us know! @Dunx in that case there is no point to split the effort and I shall just put the domain name on sale or close the page if there are no takers.</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>it's a great domain name! I'm sure Jamie would take it if you end up letting it go :smile:</td>
</tr>
</table>
<h2>3️⃣.4️⃣ <a href="https://www.drupal.org/project/react_flow">React Flow</a> - will be used with Modeler API to visually show structure of Agents and (potentially) use ECA to create agent-flows :thread: with details (edited) </h2>
<table>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>We started with some meetings and UI (not done yet) -<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/react_flow/issues/3537374" title="Status: Active">#3537374: React Flow UI Work</a></span></td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>So far we don't need a review, but we might need once we have an MVP ready - due to holidays -> we target mid-end of Sept.</td>
</tr>
<tr>
<td>Dunx</td>
<td>It's not really clear what this module is as <a href="https://www.drupal.org/project/react_flow">project page is not completed</a> or what it or this issue has to do with AI.</td>
</tr>
<tr>
<td>Tyler Staples</td>
<td>Is this going to essentially be an IFTTT (If this then that) for showing what the agent does?I like the sound of this if so!</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>@jurgenhaas</td>
</tr>
<tr>
<td>jurgenhaas</td>
<td>@Sergiu Nagailic (Nikro) Great to see you're making progress. Let me know if I can help you with anything.@Dunx I guess this is going to become an alternative to what you can see with the <a href="https://www.drupal.org/project/bpmn_io">BPMN.iO module</a>: a frontend for complex config entities.@Tyler Staples The ReactFlow component will be a UI which allows configuration of complex config entities like AI Agents or ECA. Others are possible in the future as well. And yes, the combination of those tools will get you into a position where you can build an IFTTT replacement. It's not so much about showing what the agent does, it's more like building workflow instructions for agents. However, in a future step we're considering a "re-play" feature which could be used to visually show what has happened when such a workflow got executed.</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>@jurgenhaas @Sergiu Nagailic (Nikro) mentioned in the planning meeting he could use some help connecting the react flow stuff to modeller API</td>
</tr>
<tr>
<td>d34dman</td>
<td>@Sergiu Nagailic (Nikro) does this mean FlowDrop can be "dropped" (pun intended :D) I did publish my work after our meeting in July, but didn't get any feedback, guess you were busy. While working on <a href="https://www.drupal.org/project/flowdrop/issues/3538835">FlowDrop</a> I had already made some progress regarding the modeler api integration (Please Ignore the comment as it was meant for a private discussion with Jurgen). While playing with Modeller API, I ran into limitation of the Agent structure it self, so was experimenting with custom config in FlowDrop. Let me know what you plan to do with React Flow, so that I can focus on the right thing. Its difficult to find sponsorhips for my work as am not part of Initiative so the progress has been slower.</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Oh @dan2k3k4 did realise it was ready for feedback. I'll check it out</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Last time I checked I thought you were focusing on vibing on the UIs and so the stuff you thought worked well could go into react flow as well</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Will try and get it up and running with @Andrew Belcher</td>
</tr>
<tr>
<td>d34dman</td>
<td>@yautja_cetanu (Jamie) I had a meeting with @Sergiu Nagailic (Nikro) and @Jasper Lammens but then, I didn't get any feedback from them though. Also during the early days you did express interest in such a UI but didn't had a capacity to take it into AI Initiative, So I didn't bother troubling you for any feedback. So its going on "on a slower" but steady pace. I am capturing my progress in the Roadmap.</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Cool well I'll try and get my head into it</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>I have a slight bias towards react flow generally because everything is moving towards react regardless if it's the best or not (almost all my devs hate it )</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>But v0.dev doesn't everything with react flow, XO etc</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>You don't have any demo sites where I can play with it ?</td>
</tr>
<tr>
<td>d34dman</td>
<td>regarding the technical details, I was going to have a conversation if there was going to be a collaboration :stuck_out_tongue: so defer that to later.Regarding demo, I can bring it up. For now, the project has a ddev-contrib support. So you can install it in local and enable the modules to play around. Happy to walk you through if you are interested. I can make some time for you 🙂</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>@d34dman - :wave: hey! I indeed didn't get time to get deep into the code you published. I only had some time to skim through the project files, but I didn't install and play with it locally. But after the meeting we had then, me and Jasper decided to still continue working on MVP prototype of react flavor, a bit simpler approach than FlowDrop (i.e. plugins instead of config entities & completely embrace the modeler API) - hence the result.I'll try next week to install and play with it locally, but I'll be mostly on vacation so I can't really 100% promise this :grimacing:</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>@Sergiu Nagailic (Nikro) ok I think when you're back from vacation we need to make it an ai initiative priority to decide on a direction</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>As whilst it's good to iterate and explore different approaches this is becoming important enough we need to direct our efforts somewhere</td>
</tr>
<tr>
<td>d34dman</td>
<td>@Sergiu Nagailic (Nikro) so architecture wise it would be different, that is a compelling reason indeed.</td>
</tr>
<tr>
<td>d34dman</td>
<td>That way, ReactFlow, ComfiUI, FlowDrop and BpmnIO have different un-derlying architecture iirc. Which I believe is good in a way during experimental stage. But would be nice to align on direction</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>@d34dman yeah but look we didn't spend weeks on it, we just spent a few days (~2 / 2.5) - idk where it will end-up, but from discussion with Jasper we kinda envisioned a simpler approach (i.e. no UI-based "nodes" and no separate execution handlers = but just 1 plugin; and we kinda wanted to lean towards React as @yautja_cetanu (Jamie) says).</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>@Sergiu Nagailic (Nikro) yeah I think it would just be good to have some exploration of an ai initiative wide approach where we can look at the advantages and disadvantages of them</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Like the Drupal community can keep going with lots of approaches but FTE focus should probably align if we are sending resources to it</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>Agree with Jamie, I thought it would be good to get to demo-able MVP and then decide on picking directions 🙂</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Yup agreed !</td>
</tr>
<tr>
<td>Sergiu Nagailic (Nikro)</td>
<td>@d34dman but the image (ECA Model / via Modeller) looks really good, great progress! I'll try to make time and play with it :stuck_out_tongue:</td>
</tr>
</table>
<h2>3️⃣ . 5️⃣ AI Agents Test, I’m working in the issue queue, this one needs reviews:<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_agents_test/issues/3541330" title="Status: Closed (fixed)">#3541330: Use a different model for LLM evaluation</a></span> and should have an MR in 2 hours. (edited) </h2>
<table>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>@Bisonbleu cool! Could you try and assign the items to you so I know what to give to others</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Assign all the ones to your that youre planning on working on</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Done on both…</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Great !</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Note that #3538684 is a bit of a blocker for others as it contains .gitlab-ci.yml…</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>This one now also needs reviews (Drush command is wip):<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_agents_test/issues/3541330" title="Status: Closed (fixed)">#3541330: Use a different model for LLM evaluation</a></span></td>
</tr>
</table>
<h2>4️⃣ Open Mike! Suggest your topics (and discuss them in threads) for another 23 hours. Start the topic with a number like 4️⃣ 1️⃣ , 4️⃣ 2️⃣ etc.</h2>
<table>
</table>
<h2>4️⃣ 1️⃣ What can novices do to help out?</h2>
<table>
<tr>
<td>valthebald</td>
<td>Good question! @Kristen Pol (she/her) do you think we have any low hanging fruits? Cc @yautja_cetanu (Jamie)</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Unfortunately, afaik, we haven't yet been using the standard Novice tag to tag issues that are good low hanging fruit</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Ideally, we'd start using that as a group for things that are small tasks</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>that said, one way to help is to look for issues that need review and see if any need manual testing... this is highly valuable</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td><a href="https://www.drupal.org/project/issues/ai?text=&status=8&priorities=All&categories=All&version=All&component=All">https://www.drupal.org/project/issues/ai?text=&status=8&priorities=All&categories=All&version=All&component=All</a></td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>I imagine that the team hasn't been adding the official "Needs manual testing" tag either but I do try to use that when I need to make sure things are well tested beyond code reviews</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>yeah... just checked that one and there's nothing</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>and no novice issues tagged</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>so... this will need to be part of our issue triage and grooming process as we pull in an official project manager which will be happening soon</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>@Gábor Hojtsy (he/him) may have some thoughts on this as well from a process point of view</td>
</tr>
<tr>
<td>Gábor Hojtsy (he/him)</td>
<td>I don't yet have thoughts on this.</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Yeah I've been trying to use it but it's not obvious we have that many novice tags. It's not obvious we have many issues for anything other than a senior developer , trying to get things for a normal developer</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Hard to find things for a novice ATM</td>
</tr>
<tr>
<td>yautja_cetanu (Jamie)</td>
<td>Writing tests will be something but even then they usually require lots of intimate knowledge of the domain and what to test even if they don't need much code</td>
</tr>
</table>
<h2>4️⃣ . 2️⃣ MCP in Drupal CMS 2. Showcase that Drupal is not just a consumer of AI but can also be an active participant in an AI stack.</h2>
<table>
<tr>
<td>Gábor Hojtsy (he/him)</td>
<td>What would be a great target / demo for the target audience of Drupal CMS? I think the demo from @Giorgi Jibladze was great. Maybe we can think forward a bit from there to a less proof of concept demo. (edited)</td>
</tr>
<tr>
<td>Giorgi Jibladze</td>
<td>Thanks, @Gábor Hojtsy (he/him), for raising this topic.I’d be happy to contribute or get involved in any way that might be helpful.</td>
</tr>
<tr>
<td>Giorgi Jibladze</td>
<td>Here is the demo, that Gabor mentioned, if anyone is interested in:<a href="https://www.linkedin.com/feed/update/urn:li:activity:7362470569381892098/">https://www.linkedin.com/feed/update/urn:li:activity:7362470569381892098/</a></td>
</tr>
<tr>
<td>Giorgi Jibladze</td>
<td>Before Vienna, we plan to improve the MCP Studio and the the MCP module in general even more. Will keep you posted.</td>
</tr>
<tr>
<td>Giorgi Jibladze</td>
<td>Showcase that Drupal is not just a consumer of AI but can also be an active participant in an AI stack.and @Gábor Hojtsy (he/him)I strongly agree with this. We see Drupal not only as a way to become an LLM-powered application itself (through internal AI automations and similar use cases), but also as a powerful platform for building manageable and configurable back-end systems (an area where Drupal truly shines), that can then be exposed to other LLM systems.This is why we are focusing heavily on developing an MCP server module and the tools around it.</td>
</tr>
</table>
<h2>4️⃣ .3️⃣ Split out AI Search into a separate project</h2>
<table>
<tr>
<td>kimb0</td>
<td>Discussed at length in <a href="https://drupal.slack.com/archives/C0803LX4536/p1754974639187329">https://drupal.slack.com/archives/C0803LX4536/p1754974639187329</a> but I'm still convinced splitting out AI Search into a separate project would let it move from experimental to stable more quickly without needing to be tied into the core AI module releases.</td>
</tr>
</table>
<p>Participants:</p>
<p>robertoperuzzo, Sergiu Nagailic (Nikro), Dunx, Bisonbleu, thejimbirch, Tyler Staples, bryan, Gábor Hojtsy, Kristen Pol, beautifulmind, matthews, the_g_bomb, dan2k3k4, d34dman</p>
issue