Re: do we need plone.app.customerize? was: [Plone-Users] Insufficient privileges on folder_contents

On Thu, Dec 12, 2013 at 3:33 PM, T. Kim Nguyen <[email protected]> wrote:
> Lennart, two things:
>
> For workflows TTW you don't need the ZMI anymore; plone.app.workflowmanager
> is very nice and generates diagrams of the workflow on demand.

Cool!

> I have thought a lot about how to manage hundreds of sites, each custom to a
> small or very large extent, in the (long term) easiest and least risky way.
> For many devs, repeatability is important so you do things through code and
> push your tested changes out via deployment scripts. For maintainers of
> large scale shared environments, that is not ideal, in fact far from it. The
> TTW aspects of Plone are what allowed us to deploy the way we have at UW
> Oshkosh and I'm sure at other places. Take away those TTW features and we
> can no longer support Plone here the same way.

Well, as mentioned, I don't think it's the actual TTW-part that is the
features you need. I don't think you actually need the feature to
store scripts in the ZODB, or that you have to use a text field as a
code editor, or that you have a need of not being able to version
control your templates. But that's what TTW gives you.

Once again I think we need to identify what you *actually* need, and
I'm relatively sure that none of the above things will be on that
list. :-)

//Lennart

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk