Please setup Github pages for the m2e-organization

Similar to #1650 (closed) we could need the same for m2e, the old website is gone for unknown reasons so we need to setup an alternative. (see https://github.com/eclipse-m2e/m2e-core/issues/831 )

So I'd like to ask for:

1. a repository under the m2e organization named 'eclipse-m2e.github.io'
2. enable GH-Pages for this repository
3. Upload the content from https://git.eclipse.org/c/www-deleted/m2e.git/ is possible (it seems one can't clone that repository anymore!)
4. Setup the domain https://m2e.eclipseprojects.io to point to the gh pages
5. Add an Http level 301 Moved Permanently redirect from https://www.eclipse.org/m2e/(.*) --> https://m2e.eclipseprojects.io/$1 (similar to #2058 (closed))

FYI @mistria @akurtakov @HannesWell

Please give +1 @fbricon

changed the description

Regarding the 'deleted' www-repos and the removed project websites, has there been an announcement that this will happen? Because at least Christoph and I weren't aware of that and were surprised when we noticed that the website is gone. Maybe other projects aren't aware of the situation as well and didn't notice it yet?

As part of our Gerrit shutdown plan, we've been moving project website repositories to either Gitlab or Github(the m2e issue is: #1828 (closed)), and the redirection to projects.eclipse.org is the expected end state if there was no response after a few attempts to reach the PL before the deadline.

There is some complication around using the eclipseprojects.io domain(see #732 (closed), #1991 (closed) for the discussions), so ideally any domain change would wait until #1991 (closed) is settled.

Since the project already seems to be on Github, I've created https://github.com/eclipse-m2e/m2e-website , and imported your existing content. Committers that have added their Github IDs to their Eclipse.org accounts will receive access in an hour or so when the sync tool runs.

Out publishing tool has been updated to pull from https://github.com/eclipse-m2e/m2e-website and publish to www.eclipse.org/m2e .

The original repo has been marked read-only with a pointer to the new location.

@mward Maybe it makes sense to send this to the dev list of the projects as well, AFAIK this is the official communication channel.

Also from the other ticket:

the project will be referred to the EMO for termination review.

so because PL do not react to Gitlab Issue m2e is now scheduled for termination without any notice to the rest of the team? Seriously?

I also read the issues about eclipseprojects.io and only concern I know is from existing project not want to move there location ... what mostly not applies to m2e.

About m2e-website repo, thanks for recovering content there, is there any reason not naming it eclipse-m2e.github.io right now?

Well the general expectation is that the PL would discuss these things with the committers and then let us know where they(the project) wanted things to move to.

so because PL do not react to Gitlab Issue m2e is now scheduled for >termination without any notice to the rest of the team? Seriously?

As you quoted correctly un-responsive projects would be flagged for 'review'. So I would expect the EMO team to check on some metrics(most recent commits, issue/bug counts etc) and reach out to the -dev list(or even directly to committers if there isn't a response) before declaring a project 'dead', and in need of actual termination.

And this referral hasn't happened yet(even though the due dates are well past), simply because I figure a few projects are in the same situation as m2e is/was and so this is simply acting as yet another grace period for projects to say 'whoops, sorry we missed this!'.

WRT the domain change, if you really don't care about having www.eclipse.org/m2e(or you want it to redirect to a Github pages site) we can certainly help you with that. It's not the default because of the feedback we received on the linked issues.

The caution here was to prevent any more 'splits' or 're-moves' of project websites between any more domains.

Thanks for the clarification, I'll try to negotiate with the team how to best proceed and report back.

added IT-prioritylow IT-severitylow ~40426 labels

added team:infra label

added Awaiting Feedback label

@lmisingnamem8k was there any decision made on this?

Yes we would like to have:

1. a repository under the m2e organization named 'eclipse-m2e.github.io'
2. enable GH-Pages for this repository
3. Setup the domain https://m2e.eclipseprojects.io to point to the gh pages
4. Add an Http level 301 Moved Permanently redirect from https://www.eclipse.org/m2e/(.\*) --> https://m2e.eclipseprojects.io/$1 (similar to #2058 (closed))

+1 from me as project lead

@hwellmannwr6 please also give a vote here @fbricon please also give a vote here

+1 from me as another project lead.

assigned to @jmazanek4ep

@jmazanek4ep What is the status here? There are already is https://github.com/eclipse-m2e/eclipse-m2e.github.io but there is

1. no redirect on https://eclipse.dev/m2e/
2. broken pages in https://eclipse-m2e.github.io/
3. no domain https://m2e.eclipseprojects.io/

Please give a current state and some ETA please

@kwindszus my apologies, this ticket got drowned in other issues. I am looking into it now

@claeubrich @kwindszus

Currently the website is accessible here https://eclipse.dev/m2e/

It is served from the repository here https://github.com/eclipse-m2e/m2e-website, which seems to contain the code from the old git.eclipse.org website repository. Cam you please check that the content indeed matches your expectation? If you confirm that, we can use it as a source for your Github pages. It seems that standard migration was done for your website; i.e. www.eclipse.org/project-name -> www.eclipse.dev/project-name, although I am unable to find the associated ticket.

@jmazanek4ep Thanks for the info. Is there some build pipeline involved or how is the content from https://github.com/eclipse-m2e/m2e-website ending up on the webserver https://eclipse.dev/m2e/?

How would it work when publishing to GH Pages? Do you have some links to documentation?

@kwindszus the current workflow is simply git checkout of the source repository to be served by our web server plus the http redirect.

For the Github pages setup I will probably follow this guide https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site plus configuring a custom domain and a new redirect

@jmazanek4ep Thanks for the info, but to me it seems that the original website sources have been lost during the migration. According to https://github.com/eclipse-m2e/m2e-website/blob/master/README.md it is a Jekyll-based website built from MD sources, however the master branch only contains the generated html pages (but no the MD sources). Is it possible that the MD was not transferred correctly from the original Eclipse repository? Also I am wondering how updates are populating the webserver? Is that based on a commit hook?

@kwindszus if you can identify the repository on git.eclipse.org that contains the code that is missing, I can import it to github

@kwindszus just checking if there is something left to do?

For now, there is no more todo. I will raise a new issue once we established a new website build process.

closed