Migrate Eclipse IDE landing pages to ide-wg website

//cc @sgiacomoni2as

changed title from Migrate eclipse ide landing pages to ide-wg website to Migrate Eclipse IDE landing pages to ide-wg website

I support this recommendation, but I'm not sure who the decision-maker is.

Will this change anything for a user? Or is this just background adjustments?

cc @pbuckd40

We will need to put in places redirects to avoid a broken link issue.

For example, https://eclipse.org/callisto should redirect to something like https://ide-wg.eclipse.org/release/callisto

@sgiacomoni2as Does it make sense to you to move these landing pages under the "release" sub-directory? That's what we are doing with Jakarta.ee: https://jakarta.ee/release/9.1/

That's what I was envisioning. And we would probably add a link to the current release page in the menu, to improve the overall navigability.

Hmmm I just re-read you mean the IDE Project Pages and move them under the WG. Is that really what we want to do here? WGs complement activities of EF open source projects - there is no notion of working group ownership of projects unless we are referring to spec projects which operate under the purview of the WG's Spec Committee...?

This is not related to the IDE project pages. This is content that the foundation produces to promote the next SimRel release.

@scorbett Just to let you know that we are going to get started on this task later this week.

Let me know if you have any objections! //cc @epoirier

mentioned in issue eclipse.org#53 (closed)

assigned to @epoirier

changed due date to March 31, 2022

Yes, please hold.

Unfortunately, we have not yet had an opportunity to socialize this with the Steering Committee and that should be done first. We meet again on the 22nd of February and will add this to the agenda.

Thanks, Sharon

changed due date to June 30, 2022

@scorbett Can you confirm that we have a +1 for moving ahead with this? @sgiacomoni2as said that the WG has approved this request.

I am updating the due date since we asked to hold off on this task. Therefore, it was impossible for us to complete in Q1. However, currently planning to execute this task in Q2 if we have a +1.

Christopher Guindon said (2 months ago)

For example, https://eclipse.org/callisto should redirect to something like https://ide-wg.eclipse.org/release/callisto

Just to confirm, with the eclipseide.org (!20 (merged)) the redirects would be like:

https://eclipse.org/callisto should redirect to something like https://eclipseide.org/release/callisto ?

and for newer releases:

https://www.eclipse.org/eclipseide/2022-03 to https://eclipseide.org/release/2022-03

Indeed, I wrote my comment before we started to discuss using eclipseide.org.

The redirect that we will put in place should go to the new domain as I expect that issue to be resolved by then!

@cguindon Shanda presented a document to the Steering Committee last meeting which identifies the relevant links we would mirror as an initial step.

So, yes this will not be completed this quarter.

+1 for rescheduling to Q2.

Thanks, Sharon

I think we are now good to migrate the pages listed above to https://eclipseide.org/ and set up the redirects. We will create a separate issue that involves updating the menu on eclipseide.org to include a link to the latest release page.

assigned to @zhoufang and unassigned @epoirier

@zhoufang This is the structure that I am imagining for this:

eclipseide.org/release (The landing page which always redirects to the latest current release)
eclipseide.org/release/2022-03 (current)
eclipseide.org/release/2021-12

...

eclipseide.org/release/callisto
eclipseide.org/release/europa

...

I recommend that we start by migrating everything under the eclipseide repo. They are very similar so that should help with the implementation.

For this task, the challenge will be with the older release pages since they are all a bit different.

Let me know if you have any questions!

I am not sure who to ask for permission on this - but maybe consider archiving the very old release pages rather than expending efforts on migrating them? The old pages could redirect just to the download pages?

e.g. eclipse.org/europa -> https://www.eclipse.org/downloads/packages/release/europa

or to the wiki page:

eclipse.org/europa -> https://wiki.eclipse.org/Europa_Simultaneous_Release

If nothing else, so many of the links on those old releases are currently broken it seems not worth fixing it at all.

I am not sure who to ask for the permission on this

I am fine with creating redirects for older releases. Can you provide a list of landing pages with the redirect URL that we should use?

For permission, I think you can start by communicating this idea with the WG and EPP. You can point people to this comment if they have any issues with your recommendation so that we can discuss it!

Hopefully, we can sort this out by the time we are ready to start working on these older pages. Let's aim at making a decision by the end of the month of April in regards to what we should do for every landing page outside of https://eclipse.org/eclipseide

https://git.eclipse.org/c/www.eclipse.org/eclipseide.git/tree/

Personally, I think it's safe to assume that the WG will not have strong opinions on minor details such as the older landing pages. Jonah as the EPP lead and the Plan Council Chair is more than qualified to help steer decisions about details...

Thanks @emerks for the vote of confidence.

@cguindon I will provide you an answer for all those pages in the coming days.

Thanks @jograham!

mentioned in issue eclipse.org#117 (closed)

Migrate Eclipse IDE landing pages to ide-wg website

Designs

Child items ...

Activity