Hi,

the migration is possible - we just don't have a complete guide, yet.

Please see here:
https://www.chiliproject.org/issues/516
https://www.chiliproject.org/boards/1/topics/556
https://www.chiliproject.org/issues/484

The way I used was explained in the first ticket and its discussion thread.

If you've questions to that, I'll try to help...

A current comparison is missing, I think - but here my personal thoughts:

• currently very fast development
• many new releases
• has the biggest amount of running plugins
• but old looking/not so flexible and modern GUI
• many outdated and unmaintained plugins

• modern and quite flexible GUI => Web 2.0 / Ajax
• implements some features, Redmine misses up to today
• supports newer OS / Ruby versions -> more future-proof
• allows more customizing (just needs some more docu - which will come the next weeks)
• slow user visible development (due to big changes under the hood)
• smaller amount of available plugins

I personally often thought of migrating back to Redmine - but even if they have more plugins, they are struggling with old Ruby versions, a growing number of outdated and thus not fully working plugins and a maintainer, who doesn't really care about the needs and requests of the users.

Chili is currently slow in development - but has a really good basement regarding developers and code quality. So in my eyes CP is much more future-proof and is / will be much more flexible.

ciao,
Chris

PS: Sorry for the many updates of this post - I strongly dislike the crappy textile syntax :(

supports newer OS / Ruby versions -> more future-proof

Regarding to their webpage Redmine supports Ruby 1.9.3 and Rails 3.2.9.
What do you mean with "newer OS / Ruby versions"?

due to big changes under the hood

I cannot see any activity on the repository.

modern and quite flexible GUI => Web 2.0 / Ajax

Are there any future plans for real web 2.0 GUIs similar to Google Docs?

Best Regards,
Thomas

Hi Thomas,

my last post was really the best evidence for my missing Ruby knowledge - sorry for that.

Regarding the changes for Rails 3.x support please see this topic for example:
https://www.chiliproject.org/boards/1/topics/2160

That there's only little activity currently is really a pity - but the devs promised to speed up the activity the next time (but surely not before the holidays) ;-)

What I experienced with Redmine (and other commercial + open source software projects) was the point of less maintenance of the core. Good software projects invest time to update/refactor the core and API to be future-proof, to remove obsolete code, add more convenient interfaces etc.

This task was IMHO missing in the Redmine project before the fork. Thats a big task Eric & Co. started with Chili - refactoring the whole code basis (as far as I read it here in the discussions) and refreshing the API.

I as customer had to ask myself: Which project is the right one for me - the one with a stable (but not clean/updated) core with many releases in short time - or the new and fully overhauled version with (currently) lesser updates and user-visible changes.

Currently Redmine 2.x and ChiliProject lost the compatibility with many plugins due to changes in API and/or database structure. Thats a problem of both. And (sadly for the Chili users) there are still more plugins for Redmine, than for ChiliProject.

But I see more real movement for Chili - and the planned actions for the next months will show that. I already got frustrated about the slow development, but the last infos motivated me to grant the devs some more weeks to finish their efforts (and to have calm and recreative holidays) :-)

OMG: This post sounds maybe a little bit like a fan post :-D

ciao,
Chris