Summary
Per #1934 (closed), we're deprecating support for PHP on projects websites hosted on eclipse.dev with a target date of Decemember 2024 for project websites and December 2025 for Foundation backed initiatives and project Downloads/Archives areas.
What’s been done so far
Preliminary planning and discussions about the path forward.
What needs to be done
-
**PHP on project websites on eclipse.dev: projects must migrate to static content by Dec 31, 2024 (in 8 months). Migration paths include using the PMI project page as their home page [1] or migrating to a Hugo-based static site using the EF boilerplate [2] or using your own static website, provided it conforms to the EF guidelines [3]
-
**PHP used for download/archive pages: projects must migrate to static content by Dec 31, 2025. (in 20 months). The boilerplate [1] has a section on using Jenking and GitLab CI for this purpose.
-
**PHP in EF-backed initiatives: These will be considered individually. In most cases, PHP will remain; these properties would therefore be owned and managed by the EF's WebDev team to ensure a consistent application of a code review/deployment processes across all the code that runs on EF websites. All current authors would be expected to follow this process, which we consider simple in nature, unobtrusive and standard practice for software development. Regardless of the case, we expect these transitions to be complete by Dec 31, 2025.
[1] https://gitlab.eclipse.org/eclipsefdn/it/webdev/hugo-eclipsefdn-website-boilerplate/-/blob/main/README.md?ref_type=heads [2] https://projects.eclipse.org/projects/ [3] https://www.eclipse.org/projects/handbook/#resources-website
Proposed timeline
Throughout the entirety of this timeline, the IT team will use mailing lists, eclipsestatus.io and other means of communicating with projects the upcoming activities ahead of time.
April-June 2024
- Send deprecation/shutdown reminder/notice to the Eclipse committers list.
July-September 2024
- Audit existing sites for the presence of PHP code, and create helpdesk issues for those projects with a due date of December 2024
- As of August 2024 60% of projects still have some PHP code in their websites.
October-December 2024
- Re-run audit and remind outstanding projects directly
- Send deprecation/shutdown reminder/notice to the Eclipse committers list
- Schedule/run eclipse.dev PHP service brownouts
- Remove PHP support on eclipse.dev
January-March 2025
- Begin transitioning EF backed initiatives to repos managed/reviewed by the Foundations WebDev team.
April-June 2025
- Send downloads/archives PHP deprecation reminder to Eclipse committers list
October - December 2025
- Send final downloads/archives PHP deprecation/shutdown reminder/notice to the Eclipse committers list
- Schedule/run PHP service brownouts on downloads/archives
- Remove PHP support for downloads/archives
- Complete move of EF backed initiatives to repos managed/reviewed by the Foundations WebDev team.