Moving Project websites from www.eclipse.org/shortname to eclipseprojects.io
In order to help modernize our infrastructure we'd like to move project websites from their current home under eclipse.org/shortname to the eclipseprojects.io domain.
There are a few challenges:
-
Project vservers are already deployed in the eclipseprojects.io domain(ie: che.eclipseprojects.io) so we can't easily re-use the project shortname as a subdomain without requiring more work by those project teams.
-
A limited subset of projects use some older classes created by the Foundation to access certain databases, and they won't be available on the new infra.
-
Projects can currently run PHP code directly. Ideally we should encourage them to move to static options like Hugo to help make things 'faster' and improve security.
-
The website repository is expected to be under www.eclipse.org . A few top level projects 'exploit' this layout to nest their sub-projects under their 'name'. Currently this is handled by both some coding exceptions and the filesystem layout, but that discourages automation or changes.
-
We have at least one website repo that is shared by all subprojects of a TLP, but that doesn't belong to any of them. Any changes to the checkout process needs to handle this one exception
In order to get a better understanding of the essentials the webmaster team is going to build a PoC hosted under www.eclipseprojects.io that will do it's best to mimic the current setup so that the transition should only require minimal work from the project teams(ie: URL updates) and some generic re-write rules for the webmaster team. This transition may also be a good time for projects to give up their websites if they don't want the 'burden' of updating them and would rather we just point at projects.eclipse.org
I'd like to get some feedback from everyone else and the community.