Dear developers,
the Technical Board, in agreement with the System Administration of the
ILIAS Society, has decided to use PHP 8.4 as the default PHP version for
our ILIAS 11 test platform starting from October 24th:
https://test11.ilias.de/
This change aligns with our ongoing efforts to keep ILIAS compatible
with the latest stable PHP versions and to ensure early identification
of potential PHP 8.4-specific issues (e.g. the deprecation of implicitly
nullable parameter declarations:
https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-d…).
The documented information about the reference system can be found at:
https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/docs/configuration/inst…
For explicit compatibility tests with PHP 8.3, the same installation can
be accessed via PHP 8.3 at: https://83test11.ilias.de/
We kindly ask all developers:
- Verify that your components run smoothly under PHP 8.4.
- Report/Fix any incompatibilities or unexpected behavior early via
Mantis and GitHub pull requests.
This setup ensures we can test ILIAS 11 under realistic conditions while
still allowing targeted verification against PHP 8.3 where required.
Best regards,
Michael and Rob
on behalf of the ILIAS Technical Board and the System Administration of
the ILIAS Society
--
=============================================
Rob Falkenstein
Abteilung E-Learning
Rechenzentrum der Universität Freiburg
Hermann-Herder-Strasse 10
D-79104 Freiburg i. Br.
Tel: 0761 - 203 - 67780
==============================================
Dear community members,
while restructuring our "Collaborators and Teams" on GitHub recently, we
noticed that some of you have not yet enabled two-factor authentication
(2FA), and that a few accounts are still using authentication methods
considered "insecure" by GitHub.
To strengthen the security of the ILIAS project and protect our shared
development infrastructure, we plan to make 2FA mandatory for all
contributors.
You can find detailed setup instructions here (GitHub Docs):
https://docs.github.com/en/authentication/securing-your-account-with-two-fa…
We will enforce this requirement starting November 17th, 2025.
After this date, we will begin revoking repository access for accounts
that do not have 2FA enabled.
If you have any reasonable objections or concerns about this change,
please reach out to us as early as possible.
In addition, we encourage all contributors to use "Verified Commits"
when pushing code.
- Signed commits help ensure that:
- The code you publish can be cryptographically linked to you as its author.
- The integrity of the commit history cannot be tampered with (e.g., by
impersonation or repository compromise).
Further reading and setup guides:
- How to get the GitHub Verified icon:
https://blog.ediri.io/how-to-get-the-github-verified-icon
- About commit signature verification (GitHub Docs):
https://docs.github.com/en/authentication/managing-commit-signature-verific…
- PHP.net Git hack and the importance of commit signing:
https://php.watch/news/2021/03/git-php-net-hack
Best regards,
Michael
on behalf of the Technical Board
