Skip to main content
Jump to: navigation, search

Difference between revisions of "Locationtech Forge Migration"

(What will change)
(What will change)
 
Line 26: Line 26:
 
Project Handbook
 
Project Handbook
 
* [https://www.locationtech.org/documentation/handbook LocationTech-specific variant] will be retired.
 
* [https://www.locationtech.org/documentation/handbook LocationTech-specific variant] will be retired.
* Redirect will be established to the [eclipse.org/projects/handbook/ Eclipse Project Handbook]
+
* Redirect will be established to the [http://www.eclipse.org/projects/handbook/ Eclipse Project Handbook]
  
 
== What won't change ==
 
== What won't change ==

Latest revision as of 17:53, 16 November 2017

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