Duration: 45mins
...The meeting focused on discussing the Joomla Supporters Club iniciative – a voluntary annual contribution model with digital badges and no governance rights. We also shared a new sponsorship offer and the need of a Team Leader .
Duration: 1 hour
Carlos Cámara (OD Coordinator), Joe Sonne (member), Brian Teeman (Contributor)
Welcome and Team presentation
Current financial situation
We repor
Discussion about Joomla Supporters Club initiative
The team discussed the proposal Brian Teeman presented (based on his 2009/2010 concepts and the April 2026 document). Key points:
Attendees: Anja de Crom, Claudia Weber-Lenck,Dan Atrill, Emmanuel Lemor, Brian Teeman, Herman Peeren
Not attending: Cyril Reze, Richard Gosler, Serge Billon
This was a chat meeting to go over the content of the April issue. We have a very diverse list of articles for this issue, so it will be nice to see what eventually will be submitted in time. If an article won't make it for April after all, we'll move it to May. It's good to have articles in the pipeline.
The meeting lasted around 40 minutes.
...Attendees: Adarsh Dubey, Krishna Gandhi, al ikon, Weno Hans, Emmanuel, Martin (Teamlead) - Duration: 60 minutes - Discussed 4 items on the agenda - discussed issues on the identity portal (to get to Mattermost). Thank you. Next Meeting: May 4th, 2026 (time yet to be determined - check Bug Squad channel or invitation)
The automated testing team is responsible for different kind of tests which can be run in an automated way. Mainly they are executed when authors offer code changes on Github. Here a few intersting stats about the current status:
Code style checks do help to have a unique code style accross the whole code base.
Integration and unit tests are low lewel code tests, which are testing parts of our code.
System tests are real browser tests and do test the
...