Ship with fully-tuned high-perf buildout recipes
Out of the box, Plone should come with known-good production configurations that include ZEO, pound, squid, nginx, varnish, Apache that don't require arcane knowledge to tweak
Adminjonstahl (Admin, Plone) commented
Martin's "uberbuildout" is a good start. http://www.martinaspeli.net/articles/new-uber-buildout-with-repoze-and-deliverance
Michael T commented
Don't forget Haproxy - by far the easiest to setup with buildout and better yet (IMHO) than nginx for load balancing.
Could it be possible to make this as a "service on plone.org". Every developer "states what have to be added to buildout.cfg for his product. The user uploads his current buildout.cfg, and has a UI to chose which products he wants to add and is given a new buildout.cfg
I have to agree. Buildout has begun to give us a common ground on which to focus support but we need to take it to this higher level. Not everyone should have to learn every layer before they can effectively implement plone. Beginners should be able to install a 'standard' implementation that all of us are familiar with. I think this should also include a standard testing setup (right now I see three variations on testing that don't work well together).
Adminoptilude (Admin, Plone) commented
Bear in mind that this idea forum is a bit broader than the strict definition of core Plone. I think this idea makes sense in the context of the installers, for example.
Andreas Jung commented
We have recipes for this (Zopeskel). But this functionality has nothing to do with Plone core improvements.