You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2012/12/31 23:48:12 UTC

[jira] [Resolved] (ROL-358) Migration from Moveable Type and others

     [ https://issues.apache.org/jira/browse/ROL-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glen Mazza resolved ROL-358.
----------------------------

    Resolution: Won't Fix

I don't see how we can maintain migration scripts without having detailed knowledge of Movable Type blogs, which is outside the scope for Roller committers.  If someone wishes to externally maintain such a script, keep it updated, and add a link to it from the Roller Confluence, that would be fine.  But any tasking that requires us to study up internally on competitor products, and vouch for what each of their database tables and its columns mean and how they map to Roller tables would be out of scope for us.  It's best for Roller committers to work on Roller instead of spending that time researching competitors.
                
> Migration from Moveable Type and others
> ---------------------------------------
>
>                 Key: ROL-358
>                 URL: https://issues.apache.org/jira/browse/ROL-358
>             Project: Roller
>          Issue Type: New Feature
>          Components: Database Access & Data Model
>    Affects Versions: 0.9.8.1
>            Reporter: Lance Lavandowska
>            Assignee: Lance Lavandowska
>
> Create scripts for migrating from Moveable Type to Roller.
> Should these be in SQL or some scripting language?  Perl might be a good choice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira