Community
Participate
Working Groups
I have started the migration of the content on www.polarsys.org/projects to projects.eclipse.org/projects. I'm starting with the project pages with the following mapping: www.polarsys.org/projects/polarsys.* -> projects.eclipse.org/projects/polarsys.* e.g. http://projects.eclipse.org/projects/polarsys.capella Note that a side-effect of this move is that election behaviour (Project Lead and Committer) is available on the new page. Note also, that I'm doing a quick review of the content as it's being migrated to ensure that it conforms to Eclipse Trademark Usage Guidelines. We'll keep this bug open until after we've moved all content, including releases, reviews, and proposal documents.
I've started this migration. See Bug 541051 Comment 8.
Chris, we have many dozens of "release" and "review" content type nodes that we need to migrate. I'm concerned that migrating manually will be very error prone. Is there a means by which we can export the content and migrate it en masse? (perhaps with some manual tweaking in the process) We've already migrated the project nodes. These release and review nodes will reference those already-migrated project nodes, so we may need to tweak the exported data a bit before we import it.
(In reply to Wayne Beaton from comment #2) > Chris, we have many dozens of "release" and "review" content type nodes that > we need to migrate. I'm concerned that migrating manually will be very error > prone. Is there a means by which we can export the content and migrate it en > masse? (perhaps with some manual tweaking in the process) > > We've already migrated the project nodes. These release and review nodes > will reference those already-migrated project nodes, so we may need to tweak > the exported data a bit before we import it. The migration module provides a framework for exporting and mapping content: https://www.drupal.org/project/migrate Node export might be an easier solution but I would assume that we would need to re-import the project nodes for this to work. This modules seems to leverage UUID to track node id's across different sources: https://www.drupal.org/project/node_export
(In reply to Christopher Guindon from comment #3) > Node export might be an easier solution but I would assume that we would > need to re-import the project nodes for this to work. This modules seems to > leverage UUID to track node id's across different sources: We might be able to make that work. There's likely been a few releases and reviews added since we moved the project nodes, but if we re-import the project nodes as additions (i.e. import new copies alongside the existing ones), we should be able to pretty easily move any added release and reviews to imported project nodes and then delete the old ones. I may be mumbling. I can draw a picture if that helps.
I've migrated the metadata for all active projects and releases. I have not migrated the reviews and proposals. As we migrate the mailing lists (bug 543322) and git repositories (bug 544194), we need to update the corresponding PMI metadata.
> As we migrate the mailing lists (bug 543322) and git repositories (bug > 544194), we need to update the corresponding PMI metadata. We'll also have to update project ids following the resolution of bug 552859.
Wayne already finished this. -M.
