>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3550700. --> Reported by: [breidert](https://www.drupal.org/user/135619) >>> <h2>Ticket Overview</h2> <p>This ticket is to track and improve the introduction of Quality Assurance in the AI Initiative.</p> <p>QA meetings happen on a Wednesday afternoon typically at 2.15pm (GMT) - if you would like to collaborate or share ideas, please contact maddyt. Meeting notes will be posted in the comment below.</p> <p>Currently, our working plan is to standardise the use of "<strong>Needs QA</strong>" tags, by which developers can collaborate with QA testers as needed, to help reduce bugs, offer insight, and make the AI module the strongest it can be. </p> <p>If this is requested on a ticket, please leave some test notes/test guidance for QA so they know where to look! A test note template is on the ticket below:<br> <a href="https://www.drupal.org/project/ai_initiative/issues/3554829">https://www.drupal.org/project/ai_initiative/issues/3554829</a></p> <p>Similarly, we propose popularising the tag "Needs UX" - an opportunity for developers to ask for UX review/opinion on new/ongoing work to ensure Drupal AI is meeting the needs of all users. This can also be used for accessibility checks. </p> <p>The goal with both of these tags is that QA/UX/DM contributors will be able to filter the issue queue to find issues needing their assistance, which we hope will encourage engagement and help make Drupal AI the best it can be. As this may be new territory for non-developers, it would be great if we could leave test/UX notes/guidance on replicating/where to look to ensure seamless collaboration. </p> <h2>Further Ideas/Next steps</h2> <ul> <li>Review workflow with the community</li> </ul>