By Robert Deutz on 2022-08-15 13:16 in CMS Maintenance Team

Scheduled duration: 60min

Duration: 50min


Participants: Allon Moritz (Team Member), Benjamin Trenkle (Production DC), Christiane Maier-Stadtherr (Team Member), Harald Leithner (Release Lead 5.0), Llewellyn van der Merwe (Team Member), Richard Fath (Team Member),  Robert Deutz (Team Leader), Roland Dalmulder (Release Lead 4.2), Tobias Zulauf (Release Lead 3.10)


Absent: David Jardin (Security Team Liaison), Fedir Zinchuk (Team Member), Franciska Perisa (Release Lead 4.2), George Wilson (Team Member), Hannes Papenberg (Automated Testing Team Liaison), Niels Braczek (Release Lead 5.0), Quy Ton (Team Member), Sigrid Gramlinger (CMS Release Team Liaison), Thomas Hunziker (Team Member), Tuan Pham Ngoc (Team Member), Viviana Menzel (Team Member)


Meeting Results

Code sprint team [Robert]

Robert created a doodle to find a date and shared it with the team. The wish is that people arrive Thursday in the evening and leave Sunday as late as possible. So that we have two or three days to work together. Location will be in the south of Germany, most likely in Nürnberg.


Continue discussion about

The team doesn’t think that \Joomla\CMS\Factory can be removed in Joomla5. Before we even think about it we should convert the core components to get some practice on it. 

Handling of abandoned PR’s proposal [Allon]


We want to reduce the number of open Pull Requests. With a smaller amount of open Pull Requests we will be able to concentrate better on them and will be able to assign a responsible maintainer to each Pull Requests. Like that we ensure they get into a state to be mergeable.
It also prevents situations where the author gets upset because of no reaction from maintainers.

The maintainers team will check older (older means, no relevant activity for a certain time frame, eg. 6/12/18/24 months) Pull Requests and discuss if a Pull Request should be closed. 

When there are old or abandoned pull requests which are still relevant, they can get a "Ready to takeover" label, so interested people can then search for this label and take them over. 


The proposal will be sent to team members to vote via email. If we decide to follow the proposed process, we will make a decision about when a Pull Request will be considered as old.