...
- How do we get the raw reStructured Text (not HTML!) page data out of the Zwiki/Plone, say into a series of text files (which we can then feed into a custom UWC Wiki Importer) ?
- One way would be to write a WWW::Mechanize or Selenium crawler (Adam M)
- http://en.wikipedia.org/wiki/Zwiki#Storage_backend says: "Due to the use of the Zope application server, Zwiki pages are by default stored in the ZODB object oriented database backend.", is this how it's set-up on mifos.org?
- yes (Adam M)
- JRst from http://jrst.labs.libre-entreprise.org/jrst/en/, or at the worst using Docutils (http://docutils.sourceforge.net/) via Jython, may be of interest if we have to parse reStructured wiki page text for conversion into Confluence's Wiki markup syntax.
- http://twiki.org/cgi-bin/view/Plugins/ZwikiToTWikiAddOn and/or http://www.dokuwiki.org/tips:zwiki2dokuwiki MAY BE worth a closer look? If the zwiki could be converted to twiki or dokuwiki, converters to confluence then exist https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+DokuWiki+Notes and https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+TWiki+Notes could be faster/easier then manually and directly migrating from zwiki to confluence. Need to evaluate.
- http://www.google.ch/search?q=Towards+a+Wiki+Interchange+Format+(WIF), or directly http://eyaloren.org/pubs/semwiki2006-wif.pdf and http://xam.de/2006/2006-12-19-SA-Andreas-Kurz.pdf (in German), may be too "academic" to be of direct relevance / use for this project, but may still be an interesting/inspiring read in this context?
- Based on experience gained in the java.net issuezilla to JIRA migration, a multi-step approach (pull down from Zwiki, Convert locally, push into Wiki) is much more suitable for a productive iterative workflow than the all-in-one default mode of UWC. https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+F.A.Q.#UWCF.A.Q.-Iseetheconvertedfilesintheoutputdirectory%2CcanIchangethembeforesendingtoConfluence%3F describes how to use UWC step-by-step.
Steps
- Read the Developer Kick Start page for information on contributing and getting set up. Follow the steps under
- Introduce yourself to the community - Mailing Lists
- Fill out the Contributor Agreement
- Set up your machine for development:
- If you are blocked, post questions (and an in-work patch, if applicable) to (a) the IRC channel ( http://pastey.net can be used for sharing patches) and/or (b) the mifos-developer mailing list.
- For any code changed which is not covered by tests: (a) consider creating a unit test (see AccountingRulesTest for an example). If a unit test is not practical, consider creating an integration test or an acceptance test.