Department Motions

Below the registry of the motions adopted by the Deparments and Team of Open Source Matters, Inc. divided by year.

2020

Motions adopted by the Departments and Teams

Production

Full Department

#PROD2019/001 - Involve Release Leaders in the leadership of the Production Department. (per 19/04/18)
Proposed by Harald Leithner
Motion Approved with 7 in favor, against and abstained

#PROD2019/002 - Remove the helpurl for French help in J3 (per 19/05/02)
Proposed by Harald Leithner
Motion Approved with 11 in favor, 1 against and abstained

#PROD2019/003 - Force all newly merged PRs in Joomla 4 to use prepared statements. (per 19/05/02)
Proposed by Harald Leithner
Motion Approved with 12 in favor, against and abstained

#PROD2019/004 - Enforce Two Factors Authentication in the Joomla Organization on GitHub. (per 19/05/14)
Proposed by David Jardin
Motion Approved with 8 in favor, 2 against and abstained

#PROD2019/005 - Change minimum version requirements for all browsers to n-2 and drop support for Internet Explorer. (per 19/05/16)
Proposed by Harald Leithner
Motion Approved with 7 in favor, 1 against and 0 abstained

#PROD2019/006 - MySQL Requirements for Joomla 4:<br>Option A = Keep MySQL 5.5 (EOL)<br>Option B = Upgrade to MySQL 5.6 and keep it.<br>Option C = MySQL 5.6 and upgrade it with a Minor. (per 19/05/16)
Proposed by Harald Leithner
Motion Approved with 4 (B), 6 (C) in favor, against and abstained

#PROD2019/007 - Change minimum version requirements for PHP to version 7.2 for Joomla 4.0. (per 19/06/10)
Proposed by Harald Leithner
Motion Approved with 7 in favor, against and abstained

#PROD2019/008 - Make the "CMS Maintenance Team" an Official Team with voting rights (per 19/07/04)
Proposed by Harald Leithner
Motion Approved with 7 in favor, 2 against and 2 abstained

#PROD2019/009 - Support Mentors' work at Google Summer of Code. (per 19/07/24)
Proposed by Puneet Kala
Motion Rejected with 0 in favor, 3 against and 0 abstained

#PROD2019/010 - Backend Templates (per 19/09/23)
Proposed by Robert Deutz
Motion Rejected with 6 in favor, 4 against and abstained

#PROD2019/011 - Patchtester Maintainer (per 19/10/07)
Proposed by Harald Leithner
Motion Approved with 10 in favor, 1 against and abstained

#PROD2019/012 - Change minimum version requirements for PHP to version 7.2.5 for Joomla 4.0. (per 19/11/23)
Proposed by George Wilson
Motion Approved with 10 in favor, 0 against and 0 abstained

#PROD2019/013 - Make Tobias Zulauf Release Lead for Joomla 3.10 (per 19/12/12)
Proposed by Robert Deutz
Motion Approved with 10 in favor, 0 against and 0 abstained

#PROD2020/001 - JHTML Namespace (per 20/03/15)
Proposed by George Wilson
Motion Approved with 10 in favor, against and 2 abstained

#PROD2020/002a - Remove New MVC (per 20/03/15)
Proposed by George Wilson
Motion Approved with 8 in favor, 4 against and abstained

#PROD2020/002b - Namespace New MVC (per 20/03/15)
Proposed by George Wilson
Motion Approved with 8 in favor, 4 against and abstained

#PROD2020/021 [1] Allow progressive feature's (per 20/04/03)
Proposed by Tobias Zulauf, seconded by Marco Dings
Motion PASSED with 12 in favor, 1 against and 0 abstained

#PROD2020/022 [2] Solve InputFilter “magically” returning arrays by adding an additional parameter (per 20/04/14)
Proposed by David Jardin, seconded by Marco Dings
Motion UNDECIDED, NEED MORE VOTES with 4 in favor, 4 against and 2 abstained

#PROD2020/023 [3] Policy for Full Path Disclosure (FPD) (per 20/04/22)
Proposed by David Jardin, seconded by Marco Dings
Motion PASSED with 11 in favor, 0 against and 1 abstained

#PROD2020/024 [4] There shall be no indiscriminate closing of Issues or Pull Requests (per 20/04/22)
Proposed by Marco Dings, seconded by NIels Braczek
Motion UNDECIDED, NEED MORE VOTES with 6 in favor, 4 against and 3 abstained

#PROD2020/025 [5] Minimum requirements for PHP and Databases in Joomla!4 (per 20/04/23) (per 20/04/23)
Proposed by George Wilson, seconded by Marco Dings
Motion PASSED with 6 in favor, 2 against and 4 abstained

#PROD2020/026 [6] Minimum requirements for Webservers in Joomla!4 (per 20/04/23) (per 20/04/23)
Proposed by George Wilson, seconded by Marco Dings
Motion PASSED with 11 in favor, 0 against and 2 abstained

#PROD2020/027 [7] Rebase all feature pull request against 4.1-dev (per 20/06/15)
Proposed by Harald Leithner, seconded by Benjamin Trenkle
Motion REJECTED, NOT ENOUGH VOTES with 0 in favor, 0 against and 0 abstained

#PROD2020/028 [8] Specifications for J4.1 (per 20/06/15)
Proposed by Benjamin Trenkle, seconded by Marco Dings
Motion REJECTED, NOT ENOUGH VOTES with 0 in favor, 0 against and 0 abstained

#PROD2020/029 [9] Do NOT move custom Joomla codestyle to PSR 12 (per 20/08/12)
Proposed by Hannes Papenberg, seconded by Marco Dings
Motion PASSED with 8 in favor, 0 against and 7 abstained

#PROD2020/030 [10] Create a joomla-backports github org that is going to hold the repos for backports we do. (per 20/10/08)
Proposed by Tobias Zulauf, seconded by Marco Dings
Motion PASSED with 9 in favor, 0 against and 6 abstained

#PROD2020/031 [11] Appoint Benjamin Trenkle as release lead for joomla 4.1 (per 20/06/10)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 11 in favor, 0 against and 4 abstained

#PROD2020/032 [12] RFC for RFC (per 20/11/06)
Proposed by NIels Braczek, seconded by Marco Dings
Motion PASSED with 8 in favor, 1 against and 1 abstained

#PROD2020/033 [13] Support FTP layer in Joomla!4 (per 20/11/04)
Proposed by Marco Dings, seconded by Marco Dings
Motion UNDECIDED, NEED MORE VOTES with 4 in favor, 4 against and 2 abstained

#PROD2020/034 [14] Limit usage of 3rd party services in core (per 20/11/04)
Proposed by Harald Leithner, seconded by Marco Dings
Motion UNDECIDED, NEED MORE VOTES with 6 in favor, 4 against and 1 abstained

Footnote 1

Joomla's current policy is that we only accept changes or features that work for everything that meets our minimum requirement (e.g. PHP versions, browsers, database versions etc..)
The motion goes beyond this by allowing progressive features. This allows us to take advantage of new technology for those that use it as long as there is no adverse effect to those that don't (this should also take into account the support/documentation affects on such conditional features). As an example we could look at "lazy loading" or at "same site cookies". This motion means that a PR or ISSUE should not be closed or rejected on the argument that it IS a progressive feature. The acceptance of such an issue or feature is still subject to the usual and accepted scrutiny and discussion.

Footnote 2

Add a new method parameter "$asArray" to the "InputFilterclean" method and "Inputget" to define the desired behavior for the handling of array values. The parameter accepts 3 values, defined as class constants: ARRAY_NO, ARRAY_CAN, ARRAY_MUST. Use a default "ARRAY_CAN" value in 3.x, keeping the current behavior and allowing to log deprecated usages of the method. In 4.x, use a default "ARRAY_NO" value."

Footnote 3

FPD triggered by errors/warnings/notices/deprecations within the CMS context aren't covered by the security policy, because they can be suppressed by disabling the error reporting the CMS config, which clearly is within the users sphere of influence. FPDs outside of the CMS context (i.e. files that are directly accessible because they lack a JEXEC-Check, or files triggering compile time errors) will still be covered by the policy and fixed in security releases.

Footnote 4

Closing of Issues and Pull requests PR's shall NOT be done without underlying rationale and individual reasoning in the Issue or PR. Elapsing of a time period, inactivity of the submitter are examples that do NOT constitute valid reasons in and by themselves.

Footnote 5

PHP: 7.2.5
MySQL: 5.6
PostgreSQL: 11.0

Footnote 6

Apache: 2.4
Nginx: 1.10
IIS: 8

Footnote 7

Since release of Joomla 4.0beta1 the 4.0-dev branch is in feature freeze. This means all feature pull requests have to be rebased against 4.1-dev. This should also be done for already existing PR.

Footnote 8

Relase J4.1 will focus on discussed internal document
J4.1 featureplan Benjamin will prepare a blog post for public consumption

Footnote 9

Moving to PSR 12 has no isgnificant upside in terms of reducing the amount of work and maintenance. Lets revisit with next major release.Where we have to do backport repos we than point our composer and npm config files to that joomla-backports github orgs repo

A few important things here should be said about that repo:

- We have to clearly state that we do not take over any support or officially fork that repos and projects.

- The only intention is to have a place to backport changes and improve the core to substain php compatibility as well as security support for the time that we use them in the Joomla core.

- We clearly state that the changes have to be as minimal as possible and only when it is in the interest of joomla.

Footnote 10

Problem statment: Joomla release and support cicles are quite long and somethimes longer than some dependencys reciver official support by its upstream project. For example this happend for the lessphp as well as the phpmailer project. In the first case the project is no longer maintained in the seccond case the upstream project decided to stop all support including security support for the version of PHP Mailer that we use for B/C reasons.

Footnote 11

Release Lead for Joomla! 4.1

Footnote 12

The RFC procedure will provide a procedure that will reduce the effort from the production department to analyse and scan requests and issues by placing greater onus on the individual making requests and allowing for higher quality specifications.

This procedure definition will help create that standard.

The main advantages of having an RfC procedure are

- reduced number of issues, because feature requests will be handled in the RfC repository
- less work for volunteers, because they don't write code for the trash bin, which happens too often with the current approach ("show code, then we decide")
- less useless discussion about things already decided on, because the RfC process documents the decisions (why we do it this way, and also why we don't do it the other way)
- open for non-developers, because only the first two sections of the meta document (Summary and Why Bother) are needed to start the process
- less maintenance, because the RfC procedure leads to better maintainable code
- improved communication, because the process involves other departments
- improved quality, because the process ensures architectural suitable solutions

See: https://github.com/joomla-x/joomla-standards/pull/14

Footnote 13

At the moment the FTP layer is broken in J!4 this is a release blocker either way as it has to be fixed or removed. Supporting this motion would suggest to fix it. The FTP layer is a "workaround" for hosters that run their sites with a server user that has restricted/no access to the file system in the website.
Summary of discussion:
Arguments against:: * nobiody in production has seemed to use this feature * using FTP layer is not practical as it would only work if extension developers would consisantly use the Joomla file API *
Arguments
Aguments in favor of continued support. Certain extension developers "count on"/"depend on" it being available

Footnote 14

Prohibit usage of third party services as part of core. This does NOT immediately impact existing 3rd party services but it is applicable to additions inteded for core. Existing functionality using third party services such as, but not limited to Google Captcha, Yubikey support are ultimately to be moved to core-supported extension.

Operations

Full Department

#2020/OPS/001 - Webmasters Team - No monthly meetings, but monthly reports.
Proposed by Wilco Alsemgeest, seconded by Radek Suski
Motion passed with one abstain (Karen)

#2020/OPS/002 - Webmasters Team - Feedback collection by mail and surveys with deadline of at least 1 week.
Proposed by Wilco Alsemgeest, seconded by Radek Suski
Motion passed with one abstain (Karen)

#2020/OPS/003 - Webmasters Team - All decisions to be done which involves all sites, infrastructure, work methods and thus basically everything not related to just one website, must be done by motion.
Proposed by Wilco Alsemgeest, seconded by Radek Suski
Motion passed with one abstain (Karen)

#2020/OPS/004 - Allow exception for the Volunteers Portal team to provide quarterly reports instead of each month due to the specific nature of the team.
 Proposed by Radek Suski, seconded by Jaz Parkyn
Motion passed unanimously.

#2020/OPS/005 - All Template Directory Working Group assets must be backed up and made available to the Extensions Directory Team. The Template Directory Working Group will be disbanded and any volunteer willing to work on the Templates part of JED4 is welcomed by the Extensions Directory team.
 Proposed by, Wilco Alsemgeest / Seconded by, Jaz Parkyn
Motion passed unanimously.

#2020/OPS/006 [1] All Joomla websites within our EcoSystem will always run on GPL licensed (open source) components, modules and plugins. Additionally, if an extension has been custom built by our community, it will be publicly available in Joomla's GitHub repository. Unless otherwise decided / approved by the Board of Directors.
Proposed by, Wilco Alsemgeest / Seconded by, Luca Marzo
Motion passed unanimously.

#2020/OPS/007 - Cancel Operations Department motion 2020/OPS/006 in favour of OSM Motion 2021/004. The board motion makes the department motion obsolete.
Proposed by Wilco Alsemgeest, Seconded by Jaz Parkyn
Motion Passed Unanimously

Webmasters Team

#2020/WT/001 - Joomla Backup Configuration Policy.
Proposed by Wilco Alsemgeest
Motion passed by anonymous doodle.

#2020/WT/002 - Joomla Mail Configuration Policy.
Proposed by Wilco Alsemgeest
Motion passed by anonymous doodle.

#2020/WT/003 - Joomla User Configuration Policy.
Proposed by Wilco Alsemgeest
Motion passed by anonymous doodle.

#2020/WT/004 - Identity Access Management Policy.
Proposed by Wilco Alsemgeest
Motion passed by anonymous doodle.

Footnote 1

Sites build with the Joomla CMS using components, modules and plugins will always use GPL licensed versions.
If these are built by our community, they will be available in Joomla's GitHub repository for the public, unless otherwise decided / approved by the Board of Directors

Programs

Details: Created: 23 May 2020; Last Updated: 29 July 2026

2021

Motions adopted by the Departments and Teams

Production

Full Department

#PROD2021/000 - Introduce Boostrap 5 into Joomla 4 instead of bootstrap 4 (per 2021/16/01)
Proposed by Marco Dings, seconded by Llewlyn van der merwe
Motion PASSED with 10 in favor, 1 against and 0 abstained

#PROD2021/001 [1] No more new features will be addded to Joomla 4 (per 21/03/09)
Proposed by Hannes Papenberg, seconded by Marco Dings
Motion PASSED with 12 in favor, 0 against and 0 abstained

#PROD2021/002 [2] Discontinue support FTP layer in Joomla!4 CMS (per 21/04/29)
Proposed by Hannes Papenberg, seconded by Marco Dings
Motion PASSED with 10 in favor, 1 against and 0 abstained

#PROD2021/003 - Elect Harald Leithner and Niels Braczek as Release Leads for Joomla! 5.0 (per 21/12/14)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 11 in favor, 0 against and 0 abstained

#PROD2021/004 [3] Change Joomla! Core to PSR-12 (per 21/12/14)
Proposed by Benjamin Trenkle, seconded by Harald Leithner
Motion PASSED with 9 in favor, 2 against and 0 abstained

#PROD2021/005 - Elect Roland Dalmulder and Franciska Perisa as Release Leads for Joomla! 4.2 (per 21/12/30)
Proposed by Benjamin Trenkle, seconded by Llewellyn van der Merwe
Motion PASSED with 14 in favor, 0 against and 0 abstained

Footnote 1

Joomla 4.0 is focussed on bug fixes and releasing 4.0 asap. All new feature requests will got to Joomla 4.1 or later. Existing PR's will be triaged accordingly. This decission and policy was already communicated as part of the development strategy but now is motioned by community request to remove any unclarities

Footnote 2

At the moment the FTP layer is broken in J!4 CMS, this is a release blocker either way as it has to be fixed or removed. Supporting this motion would suggest to REMOVE the support for FTP from the CMS, yet retain it as part of the the framework.

The FTP layer is a @@workaround@@ for hosters that run their sites with a server user that has restricted/no access to the file system in the website.

This motion is a follow-up of PROD2020/033 which was undecided at the moment of voting

Footnote 3

Update the code style to PSR12 as early as possible but latest for 5.0

Legal & Financial

Marketing & Communication

Events

Operations

Programs

Details: Created: 02 May 2021; Last Updated: 29 July 2026

2022

Motions adopted by the Departments and Teams

Production

Outreach

Operations

Details: Created: 02 May 2021; Last Updated: 29 July 2026

2023

Motions adopted by the Departments and Teams

Production

Full Department

#PROD2023/001 [1] The website framework.joomla.org should be switched, and the content migrated as a static page to the new manual.joomla.org and the domain redirected to that new place on manual.joomla.org (per 2023/02/09)
Proposed by Hannes Papenberg, seconded by Benjamin Trenkle
Motion PASSED with 11 in favor, 2 against and 4 abstained

#PROD2023/002 - Elect Allon Moritz and Martin Kopp as Release Manager for Joomla! 4.4 (per 2023/02/09)
Proposed by Sigrid Gramlinger, seconded by Benjamin Trenkle
Motion PASSED with 17 in favor, 0 against and 0 abstained

#PROD2023/003 [2] Delete demo scheduler Plugin (per 23/06/06)
Proposed by Allon Moritz, seconded by Martin Kopp
Motion PASSED with 8 in favor, 0 against and 5 abstained

#PROD2023/004 [3] Remove code which then breaks our B/C promise (per 23/06/25)
Proposed by Harald Leithner, seconded by Benjamin Trenkle
Motion PASSED with 14 in favor, 0 against and 0 abstained

#PROD2023/005 [4] Set mySQL minumum version to 8.0.13 (per 23/07/25)
Proposed by Harald Leithner, seconded by Benjamin Trenkle
Motion PASSED with 14 in favor, 0 against and 0 abstained

#PROD2023/006 [5] Adjust the Release Process (per 23/08/05)
Proposed by Sigrid Gramlinger, seconded by Harald Leithner
Motion PASSED with 14 in favor, 0 against and 1 abstained

#PROD2023/007 - Elect Luca Racchetti & Martina Scholz as Release Manager for Joomla! 5.1 (per 23/09/28)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 15 in favor, 0 against and 0 abstained

#PROD2023/008 - Elect Marc Dechevre & Peter Martin as Release Manager for Joomla! 5.2 (per 23/09/28)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2023/009 [6] Elect Benjamin Trenkle as second Release Manager for Joomla! 5.0 (per 23/09/28)
Proposed by Sigrid Gramlinger, seconded by Christiane Maier-Stadtherr
Motion PASSED with 15 in favor, 0 against and 0 abstained

Footnote 1

The website framework.joomla.org has very little content and at the same time is eating up quite a bit of resources by requiring PHP/codestyle/dependency-updates. These resources are better used in other parts of the project.

Footnote 2

The demo plugin has no real functionality for the core CMS and should be deleted tfor 5.0 o keep the core as small as possible. All it does is to sleep for a certain amount of seconds, when executed. Pull request is already open https://github.com/joomla/joomla-cms/pull/40147.

Footnote 3

library/src/Schema/ChangeItem/SqlsrvChangeItem.php - sqlsrv is not supported since 4.0 Upgrade Webauthnlib to Version 3 - b/c break for extensions depending on the old version (for security reasons we need to upgrade webauthnlib) plugins/multifactorauth/webauthn/src/Hotfix - not needed anymore since Joomla 5 updated the webauthn lib plugins/system/webauthn/src/Hotfix - not needed anymore since Joomla 5 updated the webauthn lib libraries/src/Log/DelegatingPsrLogger.php - b/c break because upgrading psr logger which is needed by new webauthn version, class is now final administrator/compoonents/com_menus/src/Controller/MenusController.php method resync - only used in joomla 1.6 Removal of Joomla/ldap dependency see https://github.com/joomla/joomla-cms/issues/40643 - We don't use it anymore and it is broken in 4.x anyway, afaik now all major 3rd party ldap implementation depend on it's own ldap libs Remove obsolete uninstallEosPlugin method from https://github.com/joomla/joomla-cms/pull/40711 - Not needed anymore by core because the EOS will not longer be uninstalled (should effect no one) small b/c break for a debug function in Joomla/CMS/Language/Language class - Reason abstract from framework to reduce code
Removing erroneous User : : aid attribute #40310 - this attribute is targeted to be removed in 6.0 but should have been removed in joomla 1.6

Footnote 4

See https://github.com/joomla/joomla-cms/pull/40790 for full explaination

Footnote 5

The proposal for a change of the release cycle and release timeline came from release managers for 5.0 because of the experience of the last release cycle. We will NOT change the overall release cycle with a minor version every six month and a major version every two years, but adjust the timeline between the alpha, beta and RC versions. We will have 4 alphas now (instead of 3) and 2 betas (instead of 3). The first RC will be release two weeks before the release date.
This will be more realistic with new features, testing, language freeze and general coordination.
Find the timetable in this document https://docs.google.com/spreadsheets/d/1byDrxOJSw0KaKsIhwUCeniF14ME-Kqque6QoNbTFJY8/edit#gid=0
The releases of 4.4 and 5.0 should be at the same time to avoid confusion and promote marketing.

Footnote 6

Niels Braczek stepped down already a few months ago due to health reasons. Benjamin Trenkle will replace him and be the second Release Manager for 5.0

Outreach

Operations

Details: Created: 02 May 2021; Last Updated: 29 July 2026

2024

Motions adopted by the Departments and Teams

Production

Full Department

#PROD2024/001 [1] The Production Department sets the Process described in “Proposal handling Issues/PR” as standard. (per 24/02/14)
Proposed by Robert Deutz, seconded by Sigrid Gramlinger
Motion PASSED with 10 in favor, 1 against and 1 abstained

#PROD2024/002 [2] Elect Benjamin Trenkle as Release Manager for Joomla! 5.1 (per 24/03/05)
Proposed by Sigrid Gramlinger, seconded by Harald Leithner
Motion PASSED with 18 in favor, 0 against and 1 abstained

#PROD2024/003 [3] Freeze the Joomla Framework Version 1.0 for Pull Requests (per 24/03/27)
Proposed by Robert Deutz, seconded by Sigrid Gramlinger
Motion PASSED with 15 in favor, 0 against and 0 abstained

#PROD2024/004 [4] Release Managers for Joomla 6.0 (per 24/05/22)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 13 in favor, 0 against and 0 abstained

#PROD2024/005 [5] The Production Department agrees on the updated Joomla! Development Strategy. (per 24/07/21)
Proposed by Robert Deutz, seconded by Sigrid Gramlinger
Motion PASSED with 13 in favor, 0 against and 0 abstained

#PROD2024/006 [6] Meeting Notes from Production Department meetings published after meeting. (per 24/07/21)
Proposed by Christiane Maier-Stadtherr, seconded by Sigrid Gramlinger
Motion PASSED with 11 in favor, 0 against and 1 abstained

#PROD2024/007 [7] Release Manager for Joomla 5.2 (per 24/07/26)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 12 in favor, 0 against and 0 abstained

#PROD2024/008 - Update Joomla 4.x to TinyMCE 6.x to switch to a supported version (per 24/08/15)
Proposed by David Jardin, seconded by Sigrid Gramlinger
Motion PASSED with 9 in favor, 1 against and 4 abstained

#PROD2024/009 - Elect Richard Fath & Heiko Lübbe as Release Managers for Joomla 5.4 (per 24/09/13)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 15 in favor, 0 against and 0 abstained

#PROD2024/010 [8] Cookie Manager from GSOC2021 in Joomla Core (per 24/12/08)
Proposed by Sigrid Gramlinger, seconded by Hannes Papenberg
Motion REJECTED with 2 in favor, 10 against and 3 abstained

Footnote 1

Current Situation:
The need for a decision comes from the fact that we have at the moment 855 issues including 235 labeled as Feature. Usually we have splitted responsibilities into Bug Squat works on Issues and Maintenance works on PR. This doesn’t make 100% sense when it comes to features. The Maintenance Team/Release Managers are the last line when it comes to merging, so it would be good when the Maintenance Team/Release Managers gives a response as early as possible to submitted feature requests.

Handling Issues/PRs in the future:
The Maintenance Team, Release Managers and Bug Squad make a classification like this for features in Issues:
* Issues that are not clear in goal or what is the reason for requesting that feature will be converted into discussions. If the request is well described it can be converted back to an Issue
* Issues that are not something we want to include in Joomla! Core will be closed.
* Issues that are well described and a good addition for core will be label with “Maintainers checked”
If an issue touches other areas guidance from other teams is needed to make an informed decision. This can be an accessibility, an UI/UX issue, a software architecture or other issue that needs to be addressed from another team. Maintenance Team, Release Managers and Bug Squad are the first group that are responsible for managing requests on github. But the development and the future of the software product is a department responsibility.

More Details are in the Google Doc
https://docs.google.com/document/d/1WNw_BBC2zSfV68Vj3ngv_-JuA2KOMv3dnl6z9_1JOok/edit

Footnote 2

Benjamin will replace Luca Racchetti as a Release Manager for Joomla! 5.1
Martina Scholz will remain Release Manager for Joomla 5.1 as well.

Footnote 3

The Joomla Framework Version 1.0 is used by the EOL CMS Version 3.x. Therefore, the Production Department decides to freeze the Joomla Framework Version 1.0 and that we will no longer accept Pull Request for the Version 1.0 of the Joomla Framework.

Footnote 4

Elect Philip Walton & Gary Barclay as Release Managers for Joomla 6.0.
Additionally, Tuan Pham Ngoc will advise them for technical questions but not within the role as an official Release Manager.

Footnote 5

The Production Department agrees on the updated Joomla! Development Strategy. This document replaces the old version of the document.
https://docs.google.com/document/d/1CYQrH7-G_KSsa95X0vZ-9b4splwrqj65yTFQXMVA578/edit#heading=h.uw2gybk4xvek

Footnote 6

All participants of the PD meetings will check the meeting agenda at the end of each meeting and correct the text in their team/topic area, so that the meeting notes can be published directly without further approval of the PD meeting participants.

Footnote 7

Elect Hannes Papenberg as Release Managers for Joomla 5.2. He will replace Marc Dechevre. Peter Martin stays in the position as before.

Footnote 8

Based on the GSOC21 project there is a draft of a cookie manager for Joomla core.
Integrating a cookie manager feature in general will require long-term maintenance, particularly regarding compatibility with existing and future extensions and ensuring compliance with global legal standards.
Shall the proposed cookie manager be developed and integrated into Joomla core as a standard feature, acknowledging the complexity and maintenance of this feature?

Outreach

Operations

Details: Created: 02 May 2021; Last Updated: 29 July 2026

2025

Motions adopted by the Departments and Teams

Production

Full Department

#PROD2025/001 [1] The Production Department agrees on the merge of Automatic Core Updates into 5.4. (per 25/04/08)
Proposed by Robert Deutz, seconded by Sigrid Gramlinger
Motion PASSED with 13 in favor, 1 against and 1 abstained

#PROD2025/002 - Elect Stefan Wendhausen & Harald Leithner as Release Managers for Joomla 6.1 (per 25/05/05)
Proposed by Benjamin Trenkle, seconded by Sigrid Gramlinger
Motion PASSED with 14 in favor, 0 against and 0 abstained

#PROD2025/003 [2] Set minimum supported Webservers version for Joomla! 6.0 (per 25/05/18)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2025/004 [3] Set minimum supported Postgresql version for Joomla! 6.0 to 14.0 (per 25/05/18)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2025/005 [4] Set minimum supported MariaDB version for Joomla! 6.0 to 10.6 (per 25/05/18)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2025/006 [5] Set minimum supported MySQL version for Joomla! 6.0 to 8.0.13 (per 25/05/18)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2025/007 [6] Set minimum supported PHP version for Joomla! 6.0 to 8.3.0 (per 25/05/18)
Proposed by Harald Leithner, seconded by Robert Deutz
Motion PASSED with 16 in favor, 0 against and 0 abstained

#PROD2025/008 [7] The Production Department supports the Joomla Product Strategy developed at the Joomla 8 Sprint. (per 25/10/08)
Proposed by Sigrid Gramlinger, seconded by Benjamin Trenkle
Motion PASSED with 12 in favor, 0 against and 2 abstained

#PROD2025/009 [8] The Production Department agrees on the suggested documentation of the Documentation Team (per 25/10/08)
Proposed by Herman Peeren, seconded by Sigrid Gramlinger
Motion PASSED with 11 in favor, 0 against and 3 abstained

Footnote 1

We have the situation that not so good maintained websites are often on older version of the Joomla Core. This is problematic when we publish a security release. A solution for the problem is now available and ready to get merged in 5.4.
Why a motion is needed? Usually a x.4 Version doesn’t get new features so clarify that the department makes an exception here, will make discussions easier.

What are the arguments to merge into 5.4:
- The user base for testing the feature will be much bigger as when we only do it for 6.0
- Meanwhile users are expecting this from a software
- We don’t need it as exclusive marketing feature for 6.0

Footnote 2

Set minimum supported version for Joomla! 6.0 for the following Webservers:

Apache: 2.4 (Unchanged compared to Joomla! 5.0)
Nginx: 1.26 (Increased compared to Joomla! 5.0 from 1.21)
IIS: 10 (Unchanged compared to Joomla! 5.0)

- Webserver minimum requirements are not enforced, versions are chosen by the minimum current supported version
- Issues for lower versions as set will not be fixed

Footnote 3

Set minimum supported Postgresql version for Joomla! 6.0 to 14.0

- No change to the minimum Supported Version compared to Joomla! 5.0 from 12.0
- The 14.0 will not be enforced but issues according to version lower than 14.0 will not be fixed.
- Technically enforced will be 12.0 unchanged from Joomla! 5.0

Footnote 4

Set minimum supported MariaDB version for Joomla! 6.0 to 10.6

- No change to the minimum Supported Version compared to Joomla! 5.0 from 10.4
- The 10.6 will not be enforced but issues according to version lower than 10.6 will not be fixed.
- Technically enforced will be 10.4 unchanged from Joomla! 5.0

Footnote 5

Set minimum supported MySQL version for Joomla! 6.0 to 8.0.13

- No change to the minimum Version compared to Joomla! 5.0

Footnote 6

Set minimum supported PHP version for Joomla! 6.0 to 8.3.0
- Increase to the minimum Version compared to Joomla! 5.0 from 8.1.0

Footnote 7

The Production Department supports the Joomla Product Strategy developed at the Joomla 8 Sprint: https://docs.google.com/document/d/14H_83RwTULO8zYOyeLEpXfyXYjDLIBzf9uSOlCPT2G8/edit?usp=sharing and will publish it at developer.joomla.org

Footnote 8

Developer documentation will stay at manual.joomla.org (source in Github markdown).
User documentation will be on a Joomla CMS site (under another subdomain, to be decided), based on the current docs-core.sandbox.joomla.org experiment.
The docs.joomla.org wiki will be archived; transition and organisation of processes will be decided and planned after this motion.
Details: https://docs.google.com/document/d/1U7EBxzEQPAh0UVRwy2-u041Ut9WKkDiC2zR8O13nU7c/edit?usp=sharing

Department Motions

2020

Motions adopted by the Departments and Teams

Production

Operations

Programs

Full Department

Teams

Joomla Certification Program (JCP)

Volunteer Engagement Team (VET)

Educational Outreach Working Group (JEO)

2021

Motions adopted by the Departments and Teams

Production

Legal & Financial

Marketing & Communication

Events

Operations

Programs

2022

Motions adopted by the Departments and Teams

Production

Outreach

Operations

2023

Motions adopted by the Departments and Teams

Production

Outreach

Operations

2024

Motions adopted by the Departments and Teams

Production

Outreach

Operations

2025

Motions adopted by the Departments and Teams

Production

Outreach

Operations

2026

Motions adopted by the Departments and Teams

Production

Outreach

Operations