Package organization - Why no top-level module?

Archetypes is getting really interesting, I'm looking forward to working
with it in the coming months to do some of the things I currently look to
Formulator for.

One question though: shouldn't the entire Archetypes system be arranged
under a top-level module? APE adopted this approach as it grew in scope.

It would seem to have benefits for ease of single-command CVS checkout,
single-command intallation, and reducing the number of top-level modules
Zope Products/ which aren't standalone products (maybe I'm
misunderstanding the role of ArchGenXML, generator, validation and
transform here). Doing a reorg after 1.0 and once products have been
written to the current layout would be much more painful.

Thanks.



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5