Drupal AI Contribution meeting 2025-10-06
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3549674. -->
Reported by: [valthebald](https://www.drupal.org/user/239562)
>>>
<p>Drupal AI Contribution meeting from Oct 6, 2025 at 16:00 UTC to Oct 7, 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/3548588" title="Status: Closed (fixed)">#3548588: Drupal AI Contribution meeting 2025-09-29</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/3553420" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai/-/work_items/3553420</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/3549674">https://www.drupal.org/project/ai/issues/3549674</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. And if you're up for a smalltalk, what's your take about AI "hype cycle"? Have we already passed the peak? Or maybe it's all only the beginning?</h2>
<table>
<tr>
<td>Dunx</td>
<td>Dunx - AI is like the internet was 30 years ago. We have no idea what we'll be using for. Anybody who says they know are selling something :wink:</td>
</tr>
<tr>
<td>valthebald</td>
<td>@Dunx so you're from the crowd that believes that the curve is only starting to raise 🙂</td>
</tr>
<tr>
<td>dan2k3k4</td>
<td>:wave: dan2k3k4We're still in the early phase.</td>
</tr>
<tr>
<td>Arisha Khan</td>
<td>arisha :blob-wave-reverse-gif: I believe it's the just the beginning :smile:</td>
</tr>
<tr>
<td>thejimbirch</td>
<td>thejimbirch The early early stages.</td>
</tr>
<tr>
<td>Gurwinder</td>
<td>gantal :wave::skin-tone-4:I feel like LLMs have peaked maybe, but AI in general... so much more to discover!</td>
</tr>
<tr>
<td>littlepixiez</td>
<td>Harro Harrooooo... littlepixiez here :wave:It's all the beginning... I literally went on a clothes website and thought "man, I wish AI could just pick clothes for me..." :pika-facepalm: :dress:</td>
</tr>
<tr>
<td>bbruno</td>
<td>bbruno :wave: Similar to Dunx, I feel like the only reason it feels like it’s dying down is because the only few uses we have for it so far are already saturated - we don’t know what’s to come ;)</td>
</tr>
<tr>
<td>williamsowen</td>
<td>williamsowen here! Still feels early stages for me - I imagine much more to come in the months ahead! :smile: (edited)</td>
</tr>
<tr>
<td>artem</td>
<td>admitriiev :wave:I think the peak is not yet even visible, new LLMs become smarted, some of them become ministers in Albania government 🙂 so there is still room for growing</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Hi all :wave:hm… AI (the hype) is in its pre big-bang stage… AI (the scientific domain and now technological infrastructure) is here to stay, of course, just like the Web was there to stay in the late ’90 when it was in its pre big-bang stage… (edited)</td>
</tr>
<tr>
<td>Scott Euser</td>
<td>scott_euser :wave:</td>
</tr>
<tr>
<td>Tyler Staples</td>
<td>nexusnovaz ‐ im not sure. It's exciting because it's a new. I think we're plateaued at the moment (for drupal ai) general ai i think is also slowly dying down (edited)</td>
</tr>
<tr>
<td>Nick Opris</td>
<td>Unqunq - I am eagerly waiting for the medical sector to get the help of AI.</td>
</tr>
<tr>
<td>svendecabooter</td>
<td>svendecabooter :wave:</td>
</tr>
<tr>
<td>d34dman</td>
<td>D34dman The hype is going to come in waves of awesomeness.</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>marcus_johansson - this video was released 2 years ago and I think we are still just in the pain point step that is described there: <a href="https://www.youtube.com/watch?v=jPhJbKBuNnA">https://www.youtube.com/watch?v=jPhJbKBuNnA</a>.</td>
</tr>
<tr>
<td>robertoperuzzo</td>
<td>robertoperuzzo :mario-wave: it is just the beginning :drupalparrot:</td>
</tr>
<tr>
<td>matthews</td>
<td>Howdy! MatthewS here.The AI Hype Cycle has barely begun. There will be some serious gaffes (hopefully not for Drupal) that cause it to hiccup a bit - thinks like OpenAI's inadvertent allowance for google to index "public" conversations.It all feels an AWFUL lot like it did in 1995, when I first really started to understand what the Web was because I got my first true "digital" job as a Webmaster. Same kind of energy, but this is far bigger.</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Kristen, California :wave:Hype cycle... hmm... I can go both ways... I was part of the dotcom-boom-bust so that part feels familarBut, this is a different beast so we shall see</td>
</tr>
</table>
<h2>1️⃣ Release announcements/schedule</h2>
<table>
</table>
<h2>1️⃣ 1️⃣ As planned, <a href="https://www.drupal.org/project/ai/releases/1.2.0-rc1">release candidate for 1.2.0</a> was released last week</h2>
<table>
<tr>
<td>valthebald</td>
<td>which makes it quite possible to have a stable release by the next Tuesday, first day of DrupalCon Vienna!</td>
</tr>
</table>
<h2>1️⃣ 2️⃣ What comes next - 1.3, 2.0 or both?</h2>
<table>
<tr>
<td>valthebald</td>
<td>Discussion was started by @Marcus Johansson, feel free to join if you have an opinion</td>
</tr>
<tr>
<td>valthebald</td>
<td>it's totally fine to write your thoughts in today's discussion as well 🙂</td>
</tr>
<tr>
<td>Scott Euser</td>
<td>I think we are getting pretty close with AI Search and have been merging into 2.0.x, but depends a bit on ideal timeline of AI Core/other sub-modules whether you/they want an earlier next minor to be able to add something more significant prior to AI Search stable</td>
</tr>
<tr>
<td>Scott Euser</td>
<td>Progress on AI Search kept up to date here[#3485449]</td>
</tr>
</table>
<h2>2️⃣ This week's priority issues</h2>
<table>
</table>
<h2>2️⃣ 1️⃣ <a href="https://www.drupal.org/project/ai/issues/3550366">Upgrade from AI to dedicated ECA module deletes configured models</a> - release blocker :stop: :status_needs_review: (edited) </h2>
<table>
<tr>
<td>valthebald</td>
<td>that seems to be the only release blocker for now (fingers crossed), let's see how it goes for the rest of the week</td>
</tr>
<tr>
<td>valthebald</td>
<td>there is a solution suggested by @jurgenhaas, someone else needs to review</td>
</tr>
<tr>
<td>littlepixiez</td>
<td>I have added some comments to this @jurgenhaas and added some more code to have a gander at... fingers crossed we can get this over the line :crossed_fingers:</td>
</tr>
</table>
<h2>2️⃣ 2️⃣ <a href="https://www.drupal.org/project/ai/issues/3483462">Event for checkIfEmpty check</a> :construction:</h2>
<table>
<tr>
<td>valthebald</td>
<td>this one appears in the list of priority issues for more than a month, but got missed for some reason. Hopefully this week :crossed_fingers:</td>
</tr>
<tr>
<td>Dunx</td>
<td>@littlepixiez as Marcus has replied to your comment.</td>
</tr>
<tr>
<td>littlepixiez</td>
<td>Ah apologies!! I will have a gander here</td>
</tr>
</table>
<h2>2️⃣ 3️⃣ [Agents tests] - <a href="https://www.drupal.org/project/ai_agents_test/issues/3541323">Store the test completion time</a> :status_needs_review:</h2>
<table>
<tr>
<td>valthebald</td>
<td>this one is ready for review, anyone?</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Adding a little context here. This was implemented using the new AiAgentStatusPollerService introduced in ai_agents:^1.2. See the <a href="https://www.drupal.org/project/ai_agents_test/issues/3541323#comment-16284760">how to test</a> instructions for more details…</td>
</tr>
</table>
<h2>2️⃣ 4️⃣ [Agents tests] <a href="https://www.drupal.org/project/ai_agents_test/issues/3541315">UX Tweaks</a> :blob_help:</h2>
<table>
<tr>
<td>valthebald</td>
<td>This issue can be picked by someone interested in UI/UX</td>
</tr>
<tr>
<td>Dunx</td>
<td>UX or UI? It's not 'UX' in terms of what UXers normally do, so might be better tagged as 'UI' for an admin themer's attention. Thoughts?</td>
</tr>
<tr>
<td>Bisonbleu</td>
<td>Putting this one on my weekly list of todos…</td>
</tr>
<tr>
<td>bbruno</td>
<td>Unrelated to this specific issue, but we have a team ATM <a href="https://www.drupal.org/project/ai_initiative/issues/3550408">reviewing UX</a> over the AI module (mostly the main features). Theres a lot thats not that intuitive for non-developers :upside_down_face:</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>Yeah, and we have a weekly UX call for those who are interested in UX things ... let me know if you want to be invited ... see #ai-ux</td>
</tr>
</table>
<h2>2️⃣5️⃣ <a href="https://www.drupal.org/project/ai/issues/3550077">Make setup field widget action config action support bundle wildcards</a></h2>
<table>
<tr>
<td>artem</td>
<td>I believe this one is needed for a lot of recipes that will setup field widget actions</td>
</tr>
<tr>
<td>artem</td>
<td>would be nice to include in 1.2.0</td>
</tr>
<tr>
<td>artem</td>
<td>It is already RTBC’ed</td>
</tr>
<tr>
<td>artem</td>
<td>when merged, the corresponding core issue should be also updated to include new feature (placeholders)</td>
</tr>
</table>
<h2>3️⃣ Issues waiting for review :status_needs_review:</h2>
<table>
</table>
<h2>3️⃣ 1️⃣ <a href="https://www.drupal.org/project/ai/issues/3518963">Guardrails agents</a></h2>
<table>
<tr>
<td>valthebald</td>
<td>There's a lot going in the comments under this issue, and I am not sure if it would be easy for someone to enter the discussion at this point</td>
</tr>
<tr>
<td>valthebald</td>
<td>but the topic of agents security is, of course, very important, so I'd suggest to follow this issue if you want to be "in the loop"</td>
</tr>
</table>
<h2>3️⃣ 2️⃣ <a href="https://www.drupal.org/project/ai/issues/3525367">Placeholders not available in advanced mode</a> :status_needs_review:</h2>
<table>
<tr>
<td>valthebald</td>
<td>Another stubborn issue.After initial work was done by @abhisekmazumdar, there was a comment from @Marcus Johansson which hasn't led to the further progress.Let this message be a gentle nudge 🙂</td>
</tr>
<tr>
<td>Dunx</td>
<td>I'll share internally.</td>
</tr>
</table>
<h2>3️⃣ 3️⃣ <a href="https://www.drupal.org/project/ai/issues/3549153">Use prompt entities in translation</a> :status_needs_review: :pear: (edited) </h2>
<table>
<tr>
<td>valthebald</td>
<td>most of this issue was addressed last week by @svendecabooter, but a couple of small bits were overlooked</td>
</tr>
<tr>
<td>valthebald</td>
<td>Seems like an easy pick too!</td>
</tr>
<tr>
<td>Tyler Staples</td>
<td>I'll see what I can do, though currently prepping for vienna!</td>
</tr>
</table>
<h2>3️⃣ 4️⃣ <a href="https://www.drupal.org/project/tool/issues/3539195">Base tools</a> :construction:</h2>
<table>
<tr>
<td>valthebald</td>
<td>the issue doesn't seem too active, but there's a separate project on d.o. - <a href="https://www.drupal.org/project/tool">https://www.drupal.org/project/tool</a></td>
</tr>
<tr>
<td>valthebald</td>
<td>and the current state (even in alpha!) is very promising!</td>
</tr>
</table>
<h2>3️⃣ 5️⃣ <a href="https://www.drupal.org/project/ai/issues/3518180">Use client storage instead of user session in the chat</a> :status_needs_review:</h2>
<table>
<tr>
<td>valthebald</td>
<td>...so that you can have message history that doesn't kill the page cache</td>
</tr>
<tr>
<td>valthebald</td>
<td>solution is there for someone to review</td>
</tr>
<tr>
<td>bbruno</td>
<td><a href="https://www.drupal.org/project/ai/issues/3548397">This issue</a> touched on a similar topic, I believe we'll have some merge conflicts now. Ill mention this in the issue</td>
</tr>
</table>
<h2>3️⃣6️⃣ <a href="https://www.drupal.org/project/ai/issues/3550465">Field widget action for automator on custom field</a></h2>
<table>
<tr>
<td>artem</td>
<td>This one is needed for recipe <a href="https://www.drupal.org/project/ai_recipe_seo_optimizer">https://www.drupal.org/project/ai_recipe_seo_optimizer</a></td>
</tr>
<tr>
<td>Andy Marquis</td>
<td>@artem - I had already created a placeholder in the custom field module here:<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/custom_field/issues/3535237" title="Status: Closed (fixed)">#3535237: Create custom_field Field Widget Action plugin for AI automators</a></span>. I think we should probably handle that there in the custom_field_ai sub-module.</td>
</tr>
<tr>
<td>Andy Marquis</td>
<td>FYI @svendecabooter</td>
</tr>
<tr>
<td>artem</td>
<td>@Andy Marquis it is also ok to move the plugin from my MR (AI Core project) to Custom Field project, no problem</td>
</tr>
<tr>
<td>artem</td>
<td>did you have a chance to check it, review it?</td>
</tr>
<tr>
<td>artem</td>
<td>This feature is needed for the recipe that might be featured on DrupalCon</td>
</tr>
<tr>
<td>artem</td>
<td>so if you have capacity to add this to Custom Field module and do a release today or tomorrow, that would be great</td>
</tr>
<tr>
<td>artem</td>
<td>@Marcus Johansson, sorry to ping you here, but as well, the same question of where the plugin should be placed?</td>
</tr>
<tr>
<td>artem</td>
<td>I think as it is a new plugin, it is better to move it to Custom Field project</td>
</tr>
<tr>
<td>artem</td>
<td>this way, there will be no BC issue and no need to mark as deprecated for 2.x</td>
</tr>
<tr>
<td>artem</td>
<td>or?</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>You mean the Field Widget Action plugin?</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>(I'm like 5 minutes from merging it 🙂 )</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>I set it to RTBC for now:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai/-/work_items/3550465" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai/-/work_items/3550465</a></span></td>
</tr>
<tr>
<td>artem</td>
<td>yes, Field Widget Action plugin</td>
</tr>
<tr>
<td>artem</td>
<td>in this thread Andy proposed to include it in Custom Field module instead</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>sure, that one we can do already without causing BC - I will not merge that issue then.</td>
</tr>
<tr>
<td>artem</td>
<td>good, let’s wait what he says, I hope it will be possible to include this in the next module version and also do a quick release, so that recipes can benefit from it before DrupalCon</td>
</tr>
<tr>
<td>artem</td>
<td>thank you for reviewing</td>
</tr>
<tr>
<td>breidert</td>
<td>@Andy Marquis we are planning to present some ready to use recipes at DrupalCon Vienna next week, that depends on this plugin. Therefore, we would need to know if you could include it in custom fields until then.</td>
</tr>
<tr>
<td>svendecabooter</td>
<td>Is it just about moving the code present in[#3535237]?Or would extra work be required?Does the recipe work with custom_field 3.x or 4.x?</td>
</tr>
<tr>
<td>artem</td>
<td>the recipe is implemented with custom_field 4.x</td>
</tr>
<tr>
<td>artem</td>
<td>so if the code (plugin) will be included in the next RC this would be enough</td>
</tr>
<tr>
<td>artem</td>
<td>no extra work is needed</td>
</tr>
<tr>
<td>artem</td>
<td>I believe the plugin is also compatible with 3.x (but this needs to be checked)</td>
</tr>
<tr>
<td>svendecabooter</td>
<td>and this is unrelated to[#3550437] - that got merged into ai, instead of into custom_field?</td>
</tr>
<tr>
<td>artem</td>
<td>unrelated</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>Its still compatible with 3.x. I tested this before merging it.</td>
</tr>
</table>
<h2>3️⃣7️⃣<a href="https://www.drupal.org/project/ai/issues/3550437">Custom field automator compatibility with version 4.0</a></h2>
<table>
<tr>
<td>artem</td>
<td>This one is needed for recipe <a href="https://www.drupal.org/project/ai_recipe_seo_optimizer">https://www.drupal.org/project/ai_recipe_seo_optimizer</a></td>
</tr>
<tr>
<td>Andy Marquis</td>
<td>@artem - the widget_settings key doesn’t exist at all anymore in the 4.x version. I honestly didn’t even know this existed in the ai module. Can we move this functionality over to the custom_field_ai sub-module in 4.x? The 3.x version will eventually be deprecated anyway. (edited)</td>
</tr>
<tr>
<td>Andy Marquis</td>
<td>FYI @svendecabooter</td>
</tr>
<tr>
<td>artem</td>
<td>I believe for backwards compatibility the plugin should stay in AI Automators, to not break the sites that update AI Core module but do not update Custom Field module</td>
</tr>
<tr>
<td>artem</td>
<td>It is of course a good idea to remove it in AI Core 2.x</td>
</tr>
<tr>
<td>artem</td>
<td>and only have it in Custom Field project, where it belongs to</td>
</tr>
<tr>
<td>artem</td>
<td>@Marcus Johansson what do you think?</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>Yes, any custom field types - if they want to handle the plugins, should handle the plugins. We just added it in AI core, until we have people on board to take them over. So it should go out in 2.0.</td>
</tr>
<tr>
<td>artem</td>
<td>ok, maybe for the next release we should mark it as deprecated then</td>
</tr>
<tr>
<td>Marcus Johansson</td>
<td>This is merged for 1.2.0, and as mentioned in 2.0.0 if @Andy Marquis are fine with it, we move everything to Custom Fields module where it belongs.</td>
</tr>
</table>
<h2>3️⃣8️⃣ <a href="https://www.drupal.org/node/3549664">adding validation to ai_prompt entities</a> - is this a good idea? :status_needs_review:</h2>
<table>
</table>
<h2>3️⃣9️⃣ <a href="https://www.drupal.org/project/ai/issues/3549303">Field Widget Actions saves unnecessary data to 3rd party settings</a> one more small 1-liner that fixes annoying bug, it is already RTBC’ed, just waiting for final review and merge (edited) </h2>
<table>
<tr>
<td>Marcus Johansson</td>
<td>Checked and merged</td>
</tr>
<tr>
<td>artem</td>
<td>nice! 🙂 thank you</td>
</tr>
</table>
<h2>4️⃣ Discussion issues (not necessarily code-related) :comment:</h2>
<table>
</table>
<h2>4️⃣ 1️⃣ <a href="https://www.drupal.org/project/ai_agents/issues/3542955">Extending/overriding AI agents</a> :comment: :status_needs_review:</h2>
<table>
<tr>
<td>valthebald</td>
<td>Continued from the last weekNice to see some progress here!</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>:partying_face:</td>
</tr>
</table>
<h2>4️⃣ 2️⃣ Planning the next big thing</h2>
<table>
<tr>
<td>valthebald</td>
<td>To answer the question if there should be <a href="https://www.drupal.org/project/ai/issues/3549560">1.3 release before 2.0</a>, what would you like to see in the next major version?</td>
</tr>
</table>
<h2>5️⃣ 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 5️⃣ 1️⃣ , 5️⃣ 2️⃣ etc.It is also ok to add sub-items to previous items, like 3️⃣ 8️⃣ or 2️⃣ 6️⃣ - those will be published in the correct order in the meeting transcript</h2>
<table>
</table>
<h2>5️⃣1️⃣ <a href="https://www.drupal.org/project/ai/issues/3536887">Move TextExtractor service to AI core</a> :blob_help:</h2>
<table>
<tr>
<td>svendecabooter</td>
<td>Did some analysis in that ticket on how we could generalize text extraction, with the added difficulty that we don't want to break backwards compatibility probably.Could use some input if this is a good route to take / whether we need this at all / ...</td>
</tr>
<tr>
<td>valthebald</td>
<td>@svendecabooter you keep stealing my issues :yum:</td>
</tr>
<tr>
<td>valthebald</td>
<td>that's a good take, I'll look into implementation later today</td>
</tr>
<tr>
<td>svendecabooter</td>
<td>feel free to steal it back :smile:</td>
</tr>
<tr>
<td>valthebald</td>
<td>nah, I like the way things are 🙂</td>
</tr>
</table>
<h2>5️⃣ 2️⃣ We need to tag issues for DrupalCon Vienna's contribution day that we want to focus on, especially for new contributors who'll be in mentored contributionThe official tag is Vienna2025Does anyone have any thoughts on issues that might be approachable from new contributors?</h2>
<table>
<tr>
<td>Kristen Pol (she/her)</td>
<td>This can be hard for AI issues I think, but it would be nice to have at least a few</td>
</tr>
<tr>
<td>Kristen Pol (she/her)</td>
<td>We can tag them with Novice if they are okay for new contributors (doesn't mean they aren inexperienced devs)And with Vienna2025 if we want to focus on it for ViennaAnd with both if we hope they can be worked on during mentored contribution</td>
</tr>
</table>
<p>Participants:</p>
<p>Dunx, valthebald, dan2k3k4, Arisha Khan, thejimbirch, Gurwinder, littlepixiez, bbruno, williamsowen, artem, Bisonbleu, Scott Euser, Tyler Staples, Nick Opris, svendecabooter, d34dman, Marcus Johansson, robertoperuzzo, matthews, Kristen Pol</p>
issue