Project website repository move for escet
As part of our ongoing plan[1] to modernize our services we are moving project websites from www.eclipse.org/projectname to websites.eclipseprojects.io/projectname[2].
To support this change our tooling has been updated to allow content published to a repository branch on Gitlab or Github[3]. This change does not include running website build tools(ie: Hugo), it simply expects the final HTML content to be available in the branch(the default is 'main' but this can be changed based on project needs).
So what do you need to do? Well, webmaster needs to know if the project wants to move to Gitlab or to Github. Webmaster will then work with the project via this issue and once the move is complete committers will need to update their local repository remote URLs to point at the new location.
Already moved your website repo to Gitlab/Github? Please just point us to it(repository & branch) and we'll update the project metadata to point the tooling at that location(see aove for what is expected). You can then stop(and archive) any CI jobs you may have been using soley to copy data into the existing www.eclipse.org/projectname repository.
If the project is unintersted in moving or we haven't heard from the project by the due date of this issue, Webmaster will:
- Update the metadata to use the websites created via https://projects.eclipse.org/projects, and remove the current website repository.
- Also request a review from the EMO team to make sure the project is still active if there has been no response.
[1]https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan
[2]#732 (closed)
[3]eclipsefdn/emo-team/emo#301 (comment 827101)