Hi,
I'm jumping in the conversion because some assertions here make me
jump to the roof, sorry for the superficial responses - maybe I'll
write up a longer mail later if necessary - although it seems there
have already been a number of replies :)
On May 16, 2007, at 06:52 , Andreas Schaefer wrote:
Even if that would work it is not going to do it for me. I spent some
time helping other on the users list and on the wiki and I am not
going
to pay for a tool that helps me migrate. It is only working for
2.1.5 to
3.0 which means I would need to buy another tool when migrating
from 3.x
to 4.x?
As from 3.1, Magnolia will have automatic updates, i.e the updates
should be transparent (handled by software) or well documented.
[...]
Beside that it is question of fairness in an open-source community.
The
company behind magnolia did not open-source it for the goods of their
heart but to make money as we all do.
That is simply not true (so please verify your assertions before
talking about other's fairness). As it has been said, one of the
reasons this is not oss, is because the packager is a private
incentive from Ralf; another reason is that what you pay for is
*support*. We do followup and help with migrations, you're not just
left alone in the dark with a tool and vague doc.
If anyone would come up with whatever would help migrations (be it
documents, tools or xslt transforms for export/import files) we'd
sure be more than happy to support them and accept the contribution!
Until now we didn't have time to do this ourselves. The old free
lunch adage applies.
Cheers,
g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
