[Grok-dev] the notion of "next Grok"

[Martin Aspeli]

Christian Klinger wrote:

> [1] http://svn.zope.org/Sandbox/cklinger/grok-coredev/

Just a few comments:

  - using zc.zope3recipes>=0.5.3:application and all that inline ZCML is 
pretty nasty. I'd suggest you use collective.recipe.template to generate 
the site.zcml file from a template, rather than do it in buildout.cfg. 
Having to edit buildout.cfg and re-run buildout to make a config file 
change is annoying.

  - are you sure you need to auto-checkout all those eggs in 
sources.cfg? In general, only auto-checkout if the released version 
won't do, i.e. there's been important changes since the last release. 
The aim is to be as close to the current release as possible to test as 
much as possible what people are actually using out there, and how your 
specific changes will affect them - will you get a conflict with an 
existing release that's widely used? do you need to specify a minimum 
version in a dependency somewhere?

  - if versions.cfg contains things from the KGS, consider having two 
files with version info: one for stuff related to grok that you guys 
control, and one included as a dependency that you effectively leave 
untouched. If necessary, override versions from the latter in the former 
to be explicit about your requirements above-and-beyond the KGS.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book