Loading...
 
 Error
  • Contact the site administrator. The index needs rebuilding.
Architecture / Installation

Architecture / Installation


Migration of trac users to tiki

posts: 1630 Canada
Markus Beckschulte wrote:
But you can use it for other thinks too, like in my case. It was only used for documentation and my job is to migrate to another platform, and I chose tiki.


Yup, and Tiki is great for this use case. However, we don't yet cover the software development use case with integration with source control.

It's great that you are sharing everything you learnt from the migration, as there will no doubt be others. However, migrations scripts are by their nature very tricky to maintain. No one has the sustained interest to maintain them, so they don't keep up with changes in Tiki and the other app. They are usually orphaned (no one is maintaining them)

My company (EvoluData) offers professional services for Tiki and we do help with data migration and Open Source the code for everything we can, but I don't remember anyone ever asking us for a Trac migration. In general, most who want to migrate do not have a budget.

I welcome of course that someone would volunteer to maintain a Trac to Tiki migration tool. But with my time and team, I'd rather we invest our energy on things that make Tiki better. And if we do work on importers to grow the Tiki community, it will be from apps that are

  1. More popular and/or
  2. A more direct replacement

MediaWiki and WordPress fit those categories.

We are training some junior developers and any learning task is great (Gary made the suggestion that this could be one of them). However, this seems too much work for a junior dev that is new to Tiki. This means learning two different apps at the same time, each in its own programming language. And given the uniqueness of the use case, it's not easy to get quick help from senior developers.

Best regards,

Marc

There are no comments at this time.