| [eclipse.org-committers] Proposal: deprecate PHP in project websites |
Greetings folks,
If your Eclipse project is using PHP for its website on https://eclipse.dev/ or for downloads, please be aware that we are proposing its deprecation.
It may have made sense to allow PHP project content on our servers in the past, but in today's context, it does not. Most projects now support a static website built by a CI mechanism. The same also applies to download pages, where PHP was typically used to read the content of the filesystem in real time, this can be done at build/promotion time.
Please see https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1934 for the details. The short:
- We are proposing to remove PHP capabilities for project content on https://eclipse.dev/ by Dec 31, 2024.
- We are proposing to remove PHP capabilities for project content on DOWNLOADS and ARCHIVES by Dec 31, 2025.
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Eclipse-Service/Infrastructure-changes-Guide
Do note that, in today's security context, removing PHP is unavoidable. We realize that the EF has many items in a deprecation state - either in progress, or as is the case here, proposed and in planning. This is the unfortunate consequence of maintaining an infrastructure that has not properly evolved as the environment around us has changed, and even in yesteryear's security context, are no longer fit or are simply unacceptable.
Thank you for reading. Please comment on
Issue 1934 (link above).
Denis Roy
Director, IT Services | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration
Twitter: @droy_eclipse
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature