Hi – I am looking for some objective responses on the implementation of FarCry or Plone. From what I understand, both run upon a robust application server, in Plone’s case it is ZOPE / Python and Coldfusion in Farcy’s.
I think one of the major factors in any decision is your thoughts on development platform: ZOPE/Python and ColdFusion are really quite different.
Daemon is a big ColdFusion development house so moving to a ZOPE platform is highly unlikely for us. However, I admit I have always been a fan of the ZOPE movement. Despite some bad experiences expressed here by others, I personally would not have a problem with the ZOPE/Python platform in production. We just prefer the CFMX/J2EE platform story, and the FarCry way of managing content.
There is a lot of info on the net about Plone, and there are many international organisations that are extending the code and supporting it all over the world. There are also numerous publications available through Amazon about Plone, and developing web sites with Plone. I am wondering about the future of FarCry and what the intentions for the product are?
ZOPE/Plone have been open source a lot longer than FarCry CMS -- so there is naturally a larger culmination of online resources. Plus the open source "mind set" is less well understood in the CF community as a whole.
In terms of intentions, Daemon is fully committed to moving FarCry forward and supporting the ever growing community of FarCry developers (as are many other companies and individuals for that matter).
This year we have several plans for moving more and more information and resources into the public domain. This has been somewhat hampered by our success supporting the platform commercially in that we've been very busy servicing support contracts, training/mentoring and development engagements. Obviously our resources have to be geared up to provide the best possible commercial support before we start servicing the open source community.
Another transient issue is the 2.3 release. The localistion effort has been a little more time consuming than we originally anticipated. So we've been dedicating what resources we have to getting the code base right.
Moving forward, we're looking at a variety of initiatives including:
- better co-ordination of the documentation efforts of daemon staff and those outside of Daemon
- bringing on more farcry_core commmitters and decentralising many of the less critical system bits to developers external to the daemon engineering team
- opening up access to the FarCry issue tracking database (again)
- publishing a road map for future versions of FarCry, and a rough timeline of milestone releases
Of course none of this even touches on our committment to continuous improvement of the core code base.
One thing worth considering is that FarCry CMS is fully supported commercially. Daemon provides both support and training for FarCry developers and contributors. This is something that may be more difficult to arrange for the ZOPE/Python platform.
Either CMS is going to require a steep learning curve, and I don’t want to commit our organisation to either one without a full investigation of each.
One universal issue with CMS evaluation is that they all approach things differently. Even the vocabulary is not the same. Feel free to pepper us with questions :)
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
