Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Locationtech Forge Migration

Revision as of 17:53, 16 November 2017 by Wayne.beaton.eclipse-foundation.org (Talk | contribs) (What will change)

On December 11, 2017, the Eclipse Webmaster team will begin to migrate the Locationtech.org forge into the Eclipse.org forge.

Motivation

To improve services to the working groups:

  • Tighter integration with the Eclipse community and infrastructure.
  • More reliable, and up-to-date infrastructure.
  • Lower cost, lessen maintenance complexity, improve response times.

What will change

Code Forge items, such as Bugzilla, forums, will be migrated.

Builds

Downloads

  • Downloads hosted on download.locationtech.org will be moved to download.eclipse.org
  • We will set up redirects

Top Level Project id will change from "technology" to "locationtech"

  • Components in IPZilla will change from (e.g.) "locationtech.technology.geogig" to "locationtech.geogig"

Data from the LocationTech PMI instance will be migrated to projects.eclipse.org

Project Handbook

What won't change

www.locatontech.org website and @locationtech.org mailing lists will remain in place. Namespaces, such as org.locationtech.* will persist.

Git repositories on GitHub (github.com/locationtech) unchanged

Migration items

Beginning Dec 11, 2017, the Webmaster team will migrate the items below to the Eclipse.org forge.


__

Back to the top