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.5MySQL: 5.6
PostgreSQL: 11.0
Footnote 6
Apache: 2.4Nginx: 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 documentJ4.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 repoA 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.1Footnote 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
Full Department
No motions yet
Teams
Joomla Certification Program (JCP)
No motions yet
Volunteer Engagement Team (VET)
No motions yet
Educational Outreach Working Group (JEO)
JEO 2020/001: Define a new objective for the working group to create a proposal that covers defining educational resources with the aim of becoming an official Joomla program.
Proposed by: Todd Woodward, seconded by: Laura Gordon
Motion passed unanimously.
JEO 2020/002 (23/10/2020): To adopt the team’s mission as the following: “To be a hub of teaching tools and resources for those who want to teach and learn Joomla around the world.” and the tagline “Entice. Engage. Educate”
Proposed by Laura Gordon, seconded by Todd Woodward
Motion passed unanimously.