In response to Carlos's post...

http://blog.delaguardia.com.mx/index.php?op=ViewArticle&articleId=84&blogId=1

"I wholeheartedly support what you (and Andreas, and Andy McKay, and Jon Stahl, and Joel Burton, etc.) are saying on this point.

The people ripping out TTW and preaching multicomponadapterfaces don't, in my opinion, sympathize with civilians. They are building machinery to scratch their own itches, which is logical. However, they need to stop claiming they are scratching the civilian itch.

At the end of the day, us civilians need to rebuild the environment meant for civilians. It's our itch, we need to be the ones to scratch it.

Posted by Paul Everitt 19 Oct 2007, 08:48"


I've been trying to find a way to say.. "Hey guys.. you've made this harder for those of use who deal with clients every single day." It's getting harder and harder to convince clients that Plone isn't going to lock them down into something that can only be modified by a select few at a phenomenal rate. I realize as someone who is not a "core" contributor (I don't code.. I evangalize.. I sell Plone .. I convince large clients that using Plone instead of Sharepoint is in their best interest..if it in fact is in their best interest..it really depends on the requirements)

I can appreciate that the recent changes will help to speed development..but the fact of the matter is.. clients latch on to Plone so they can in fact manage their own intranets. We consult, we build.. and we hand off.. that's the idea. Integrators take what developers have built and customize it to meet the clients requirements..

Plone 3 is gorgeous and fantastic and only getting better .. and as an integrator who has been using Plone since the beginning I have to say it has become a powerful contender in both the CMS and ECM landscape.. but why alienate those who have to work with clients who use Plone on a daily basis? Why make it harder to guide a client through making a small change..?

TTW customization may be the evil stepchild..but it's a necessary evil.