Capella website migration to mbse-capella.org

Summary

For Eclipse Capella project we would like to migrate it to the link http://www.mbse-capella.org/ instead of https://eclipse.dev/capella/. In fact, Thales is the owner of this domain name. What's the process please ?

Thanks !

Priority

• High

marked the checklist item High as completed

I think there are a couple of issues we'll need to work through as part of this.

1. In order to provide freedom of action and a vendor neutral space the Foundation will need to own the domain. Webmaster can coordinate that transfer with the relevant technical staff/owner at Thales.

2. We provide limited support for hosting sites, the options essentially being our eclipse.dev service or Github pages.

@wbeaton am I forgetting anything?

It looks like you've got it covered.

Thank you for your feedback! It suits us well with hosting code on Github pages as is currently done. We are waiting for feedback from Thales so that you become the owner of the domain before July 1st

Until the domain transfer is complete, could you please not migrate to eclipse.dev/capella and not report the new Eclipse Capella URL to Google Search Console? Indeed it would not be well thought out for communication, for SEO / ranking to move twice once on eclipse.dev then on mbse-capella.org

Thales has agreed to transfer ownership of the "mbse-capella.org" domain name to the Eclipse Foundation, with a specific requirement: to maintain the current redirection of "forum.mbse-capella.org" to the existing server (IP 188.166.100.210).

Note that this server is presently hosted on an infrastructure managed by Obeo (a Discourse instance hosted by Digital Ocean). This situation is functioning effectively and Obeo agrees to continue investing in the operation of the forum and commits to maintaining a high SLA. We think also that the URL stability of existing messages is critical.

If Thales transfers the "mbse-capella.org" domain name to the Eclipse Foundation, @wbeaton @mward would you agree to maintain the DNS redirection and the management of the forum as it is currently?

@wbeaton can correct me, but this forum would seem to fall under the '3rd party services' section of the EDP, so as long as Thales & Obeo are willing to continue operating it in an open,transparent and meritocratic way, it should be fine. We'd also need assurance that should this service be 'terminated', we are notified so we can clean up the record.

The Eclipse Security team has been doing a lot of work to try and bring our various sites(including 'external' resources like this) up to modern standards, so they may ask for changes/fixes once the site has been scanned.

If that sounds ok to you I think we can move forward with this.

Yes, we agree with these two conditions. Thanks.

assigned to @mward

added IT-prioritymedium IT-severitylow ~21670 statewip team:infra labels

Hi,

We are ready to initiate the transfer of domain, @mward @wbeaton are you ready on Eclipse side ? If so, I will remove the transfer protective mechanism , so you will be able to initiate the domain transfer.

Thanks

What is the additional process to follow for the transfer domain process,

Maybe some document as the "Trademark and Domain Name Assignment Agreement" from https://www.eclipse.org/legal/ ? even if there is no Trademark to transfer here ?

Regards

No additional process is required. We already own the trademark.

We ready on the infra team side of things. Are there any other DNS records that would need to be preserved?

Nice, Does I send the AUTH INFO to webmaster@eclipse.org ?

All we should need is the transfer code, and then we'll start the process.

I have sent you the code by mail.

There was only one redirection from forum.mbse-capella.org to an existing server (IP 188.166.100.210)

I've begun the transfer process.

The domain transfer has finished and the change of DNS to our provider is in progress and should complete in a few hours.

FYI the forum which should be at forum.mbse-capelle.org is no more available. I suppose that it is related to the transfer.

The forum is back, but the actual website doesn't seem to be functional. I don't know if that's a side effect of OVH no longer 'hosting' the domain or what.

Hi, thanks. Forum works properly

For the root https://mbse-capella.org, it seems that DNS propagation is now cleaned with no redirections towards OVH default pages.

Can you add a record from https://mbse-capella.org to refer the Eclipse site behind https://eclipse.dev/capella (hosted on Eclipse github repository https://github.com/eclipse/capella-website)

Thanks! Regards

I've added a couple of redirects for www.mbse-capella.org and mbse-capella.org to eclipse.dev/capella.

Are we done?

Hi,

I think a redirection toward eclipse.dev/capella is not working as expected (e.g https://mbse-capella.org/arcadia-reference.html doesn't work whereas this page exists on the github website repository. It displays the main mage https://eclipse.dev/capella/).

We would like to use mbse-capella.org as the main visible url towards the Eclipse Capella website.

Thanks

I've updated the redirects to keep the URI so that links pass through correctly.

We don't support 'alternate' domain names for content hosted on eclipse.dev, so if you really want to use the domain as such you have a couple of options:

1. Use Github pages as your website repo is already on Github(we can help set this up)
2. Use a different 3rd party service to provide the website(we'll update the DNS records) and provide 'self support' for that service.

In case some details may have been lost in this ticket:

• The EF provides project website hosting and support via https://eclipse.dev/projectname only.
• Projects can optionally host their project website elsewhere - but the hosting task is up to the project. The EF does not manage, maintain and support this option.
• The EF must own project domains, as the trademark belongs to the EF. The EF can configure the domain's DNS records to point to the service of your choice. The EF can also host DNS service for the project, and point DNS records to the address of your choice.
• For hosting a website, most projects choose to use GitHub pages, but this is not the only option. Alternatively, the https://eclipse.dev/projectname website can be fronted by a content delivery tool, such as CloudFlare. Again, the onus is on the project to set this up, as the EF only provides project websites via https://eclipse.dev/

I'll close this ticket as I believe everything is complete. Please reopen if you need additional assistance.

closed

mentioned in issue #3845 (closed)

mentioned in issue #3874 (closed)

mentioned in issue eclipsefdn/emo-team/emo#221