Website Git repository move
This has already been in the works for a while (see e.g. eclipsefdn/helpdesk#1 (closed)), and has been announced a couple of times (see e.g. https://www.eclipse.org/lists/eclipse.org-committers/msg01347.html), but now it seems it is really happening. See eclipsefdn/helpdesk#1793 (closed) for the 'request' from the Eclipse Foundation IT team specially to our project.
Website repo move (in progress)
The Eclipse Foundation is closing the old cGit server. See https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan. As part of this, we have to move our website repo. We can choose to move it to GitLab or GitHub. Given that we use GitLab already, that would be the obvious choice for us.
Steps:
-
Webmaster will move the repo for us, and ensure the deployment from the Git repo to the actual website is changed as well. -
We will have to update our deployment script, to commit new website releases to a different Git repo. We should check the branch name as well. I assume permissions are not a problem, as Jenkins can already checkout our code from GitLab, so the correct credentials should already be present. (!401 (merged)) -
If you have a local clone of the website repo, you need to make a new clone or update the remote of the existing one. -
After all these changes, we may want to check the information about our project in the PMI, to see whether that all correctly reflects the new situation.
I don't expect much issues here.
Website URL change (being reconsidered)
They also will be changing our website URL from eclipse.org/escet
to websites.eclipseprojects.io/escet
. See eclipsefdn/helpdesk#732 (closed).
Steps:
-
Webmaster will take care of the actual move. -
It seems redirects will be added, including for deeper links. See eclipsefdn/helpdesk#1427 (closed). I assume this holds forhttp
andhttps
and with or withoutwww
, but I'm not sure. We should test that. -
We may want to update all links in our repo to the new canonical URLs. -
After all these changes, we may want to check the information about our project in the PMI, to see whether that all correctly reflects the new situation.
I'm not sure I like the change. We've been telling everybody about our move to the Eclipse Foundation, including the URL to remember, and now they're changing it. But at least redirects are in place, so users should still arrive at the right place. However, I personally regularly type in eclipse.org/escet
in a browser to go to the website (faster for me than clicking a bookmark), but with the longer URL I'm not sure that is efficient anymore.
Getting started
I'll inform the webmaster that we opt for GitLab. For the rest there is no choice.