simplicity proposal

[amleczko]

I would like to propose a similar but more simple approach:

• in the root of the buildout we shouldn't have any lazy configuration - only the one that is being used (probably symlinked)
• in ./config/ I would suggest to use a convention that everything that starts with _ shouldn't be used as a starting configuration (aka symlinked in root)
• development.cfg should be only (one file that has all the dev sections)

[ale-rt]

I would prefer to keep the old approach because:

1. developer are used to it
2. I feel strange telling people to edit config/_base.cfg :)

It seems to me more complicate rather than simple... just my 2c!

[amleczko]

1. The problem with current situation is that in different deployments you end-up with a lot of garbage in the root of the buildout. I would like to avoid it. And what you actually need is ONE buildout configuration per deployment.
2. The _base.cfg convention is just a proposal - it can be of course kept without _.

[ale-rt]

I see your point, especially the mess part :) What about creating two folders:

• config: containing the .cfg files that drive your buildout
• customizations: containing the .cfg files that specialize your buildout (if you prefer another name your welcome!)

[amleczko]

New update:

• in ./profiles we can keep top level cfgs (development, production, etc)
• in ./config we can keep the rest (plone, base, etc)

[ale-rt]

Ok for me!