Mautic Community Product Team - quality process

Attendees

• John Linhart

• Ekke Guembel

• Ruth Cheesley

Apologies

• Norman Pracht

Notes

• Ekke started the discussion in the Council about bug fixes and how to get them out quicker, Norman suggested whether we should accept and merge PRs for bug fixes without tests, because otherwise it blocks us getting fixes out to our users.

• Ekke shared his thoughts on the challenges we have right now with the bug situation

• Talk together (one time) to find the top xx bugs/issues that we need to fix and prioritise those (some might have PRs, some may need to get fixes created etc) - for example we could focus the upcoming community sprint just on quality to blast through that.

• Look at what PRs we have, and how we can get the top 10-20 merged.

• John: Perhaps we could make this the focus for the upcoming community sprint

• We could give more tuition / guidance on how to write good tests - John will try to write something once Mautic 7 is done.

• Ruth shared that there's plans to hire someone to work full time for Mautic, part of their work could be focused on helping to write tests if bug fixes are provided without tests.

• Ekke also asked for clarity on where tests are required, when should you use unit / functional tests.

• Let's create a way for people to submit their top priorities in advance of the sprint

• Could use the portal but Ekke worries people don't have an account / it's too complex

• Could use GitHub but it's even more complex/difficult

• A Mautic form which we can export into a Google Doc / print would be easiest

• Ekke will create a draft and pass it to Ruth and John for review

Actions

1. John will write up some guidelines on how to write good tests after Mautic 7 alpha is released

2. Ekke will create a draft form for people to submit their top priorities of bugs/issues and share with others for review