[Zope3-dev] Controller package name

[Matt Behrens]

I'm currently working on an installation, control, and configuration
system for Zope 2.  Briefly: a 'zope' script is installed on the
system that can be given commands, such as 'zope start instance',
'zope stop instance', etc.; all but a few of those commands are
defined by and implemented by a special package that is part of the
software home, currently 'ZopeControl'.  Basically, the utility
imports this package, and calls the function corresponding to the
subcommand given.

I don't see any reason why this scheme could not someday be extended
to Zope 3, without having to enhance the 'zope' binary.  The only
thing it needs is a package name that it can import out of the
software home to implement control functions. 

Opinions?

Ideas:

1.  Control (top-level package); pro: short, con: pollutes top-level
namespace (not really a problem in Zope 2...?)

2.  Zope.Control; pro: no pollution of top-level namespace, con:
does not really fit in the Zope 3 'Zope.App' scheme

3.  Zope.App.Control; pro: fits Zope 3 well, con: extra deep package
for Zope 2, but given Zope 2's organization or lack thereof, this
is probably not a real big issue

4.  ZopeControl; pro: no changes to what I'm currently doing, con:
pollutes top-level namespace

Of course, other ideas are also welcome.  I'm not implementing in
Zope 3 yet (I will want to talk to some people first), but picking
the package name is the important part now as I plan to wrap up the
control utility for Zope 2 in the next few days.