Allowing migration of a project from one site to another is not obvious. It implies that a project can be serialized to an external representation on site and then deserialized on any target site. Current CDE are built by gluing existing tools like CVS, majordomo, Telnet Access, FTP. Their serialization is complex. The only data that can be extracted from a project is the source code tarball. When people are moving their project, they loose their forums, activities, download area, mailing list archives and wiki pages. LibreSource allows to migrate resources from a LibreSource server to another.Users can dump a subtree in an XML file and restore it to another LibreSource server. Thus projects are not bound to a centralized server.
Export
Users can at any time use the "xml" action on a node. Figure 1 - XML export action This will dump an XML file containing the XML representation of subtree rooted at this URI.<?xml version="1.0" encoding="UTF-8"?> <libresource:libresource-dump original-host="potiron.loria.fr" date="21-10-05 11:38:20" original-root="/documentation"> <kernel:node owner="/users/jouille" uri-part=""> <kernel:acls-list> <kernel:acl> <acl:owner type="Group" uri="./authors"/> <acl:permissions> Kernel:READ,Kernel:CREATE,Kernel:UPDATE </acl:permissions> </kernel:acl> </kernel:acls-list> <kernel:properties> <kernel:property key="libresource-web.menu"> (...) </kernel:property> </kernel:properties> <kernel:resource shortName="LibreSource Documentation" service="LibresourceWiki" type="Page"> <wiki:page lastEditor="Florent Jouille" lastEdited="18-10-05 01:07:03"> <page:name> LibreSource Documentation </page:name> <page:content> (...) </page:content> </wiki:page> </kernel:resource> ...