>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555609. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h2 id="meeting-overview-topics">Meeting Overview / Topics</h2> <ul> <li><strong>Team Capacity &amp; Resources:</strong> The team reviewed the available resources, acknowledging that in a practical sense, there are <strong>two primary teams available to support UX requests</strong>: Aidan and Emma's group, and the 1x team.</li> <li><strong>Handling Complex Issues:</strong> A workflow was discussed for tackling complex UX problems (like the AI Chatbot block settings). The consensus was that these issues require offline collaboration within smaller teams before bringing a proposed solution to the wider group for a quick review.</li> <li><strong>Team Capacity &amp; Resources:</strong> The team reviewed the available resources from 1x and discussed how to best allocate time for both planned projects and reactive UX requests.</li> <li><strong>Tooling (Drupal Starforge):</strong> The team looked at the current "Needs UX review" board in Starforge and discussed the need for a more robust Kanban board that maps to the team's defined workflow.</li> <li><strong>AI Dashboard Status:</strong> The dashboard functionality and styling are nearly complete, with the exception of the Project Browser integration. A first stable version is almost ready for release pending a final review.</li> </ul> <h2 id="decisions">Decisions</h2> <ul> <li>The <strong>AI Dashboard</strong> is ready for a release once it receives a final internal review with 1x Team</li> <li>Complex UX issues will be handled by smaller, focused teams offline. Only the proposed solution will be brought to the main Monday sync meeting for a brief sanity check, not a deep discussion.</li> <li>The <code>Needs UX manager review</code> tag will be used as a mechanism to escalate particularly complex issues that require broader context or senior-level input.</li> <li><strong>On Issues Tagged "UX" Component</strong> There's a difference with "UX" component on AI project vs "Need UX Review" / "Needs UX manager review". One is the area of work vs "needing help" so Zoocha should not add the tag "Need UX Review" to issues with "UX" component unless help is specifically requested by the issue creator.</li> </ul> <h2 id="questions">Questions</h2> <ul> <li>What is the process for getting the necessary permissions to assign issues to other team members on Drupal.org?</li> </ul> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Bruno / 1x Team:</strong> Get a final internal review on the AI Dashboard to proceed with the first stable release.</li> <li><strong>1X Team:</strong> Confirm the team's expected weekly capacity for taking on new UX issues (e.g., number of hours, types of issues) for the new year. Currently scheduled on Wednesdays. </li> <li><strong>Isla:</strong> Confirm with Madeline/zoocha regarding the capacity and responsibility for managing the daily triage of <code>Needs UX review</code> issues.</li> <li><strong>Aidan &amp; Emma:</strong> Continue to use their working sessions to deep-dive complex issues and prepare summaries for the broader team. Currently scheduled on Wednesdays. </li> </ul> > Related issue: [Issue #3555608](https://www.drupal.org/node/3555608)