Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Locationtech Forge Migration"
Line 14: | Line 14: | ||
== Migration items == | == Migration items == | ||
+ | Beginning Dec 11, 2017, the Webmaster team will migrate the items below to the Eclipse.org forge. | ||
+ | |||
* Bugzilla: https://bugs.locationtech.org/ | * Bugzilla: https://bugs.locationtech.org/ | ||
* JIPP - https://ci.locationtech.org/ | * JIPP - https://ci.locationtech.org/ |
Revision as of 11:55, 3 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.
What won't change
www.locatontech.org website and @locationtech.org mailing lists will remain in place. Namespaces, such as org.locationtech.* will persist.
Migration items
Beginning Dec 11, 2017, the Webmaster team will migrate the items below to the Eclipse.org forge.
- Bugzilla: https://bugs.locationtech.org/
- JIPP - https://ci.locationtech.org/
- Wiki (including private SC Wikis): http://wiki.locationtech.org/Main_Page
- Downloads (if applicable)
- Nexus - repo.locationtech.org
- Project Handbook
__