On Fri, Aug 13, 2010 at 16:32, Kirst Martin Wolfgang <[email protected]> wrote: > > On Wed, Aug 11, 2010 at 14:52, Kirst Martin Wolfgang > <[email protected]> wrote: >> > Hi, >> > >> > I'm near to finish my MediaWiki2XWiki migration "toolkit". >> > I've developed such, to migrate our homegrown MediaWiki installation >> > to XWiki. >> > The footprint of our Wiki is about 230 pages with around 570 >> > attachments. >> > This will end up in round about 150MB of data. Not that big, >> > but to much to migrate it manually ;-) >> > >> > I'm dumping the MediaWiki content (exported XML) into wikimodel >> > and wrote a XWiki/2.0 serializer. After resolving all templates >> > and downloading the attachments, they get renamed to fit the XWiki >> > rules. >> > Afterwards they are uploaded automatically (including all files and >> > images) >> > to your XWiki instance. >> > >> > The process is splitted into two steps: "extraction and preparation" >> > and "uploading". Everyone with some basic skills in Java and Eclipse >> > can use this "toolkit". >> > But it doesn't claim to be an end user ready to use product ;-) >> > >> > I want to contribute it to your XWiki Code section (apache license). >> > >> > Any doubts from your side or I'm free to do so? > >> Note: there is a wiki importer framework in process (with a MediaWiki >> module working POC already) on >> > http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-wikiimporter/. >> It's supposed to be run inside XWiki but most it's code does not >> really need to be run inside XWiki (basically only the part that save >> the converted document needs that). >> >> Also there is already an official XWiki serializer you can find in the >> XWiki Rendering framework (see >> http://code.xwiki.org/xwiki/bin/view/Modules/RenderingModule) that can >> be used outside of XWiki. The wiki importer framework is based on >> XWiki Rendering module. > >> That was the note, now let's say competition is good so lets go for it >> and at some point we should try to share as much as possible the work >> done ;) > > Interesting point. > I've watch at it, but it seems to be a different approach to me. > Cause, I've had a more complete batch migration in mind, not so much > focussed on having a fancy wizard for.
I don't understand what you mean here, wiki importer goal is to import complete wikis. The UI part is just on the framework side and when you wriite a wiki importer module you don't really care about that and just declare what you want to get as parameter (the file containing an exported wiki, the URL of a wiki to import using REST, etc...), then you do whatever you want with this. IMO both project could use the exact same code for the MediaWiki -> XWiki convertion which is what is in the MediaWiki module of wiki importer, then the UI and the way to store the produced documents depends of the tool. > Additionally setting up my Eclipse workspace with just XMLRPC-API and > wikimodel was way easier ;-) So it was simpler to patch/enhance > wikimodel > for my tasks. With M2Eclipse it's very easy to use XWiki Rendering in a new project. > But as I read on page 'RenderingModel' your importer also uses > wikimodel. > Thus my patches also benefit your project :-) Actually wiki importer use XWiki Rendering which use WikiModel specifically for the MediaWiki parser but use it's own XWiki 2.0 serializer, use Doxia for other languages etc... > And of course I'm open for sharing work and thoughts. > > Regards > Martin > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
