[Zope3-dev] Re: zopeproducts, yet again

[Fred L. Drake, Jr.]

Jeffrey P Shell writes:
 > I hope it doesn't need one.

It won't; we already have all the package-identification we need via
ZCML.

 > This is my concern about 'zopeproducts', 
 > which I acknowledge has NOT been polluted with core elements, like Zope 
 > 2's Products package has.  But with 'zopeproducts' being mentioned in 
 > the current "how to build a product" system, I'm worried that it will 
 > rapidly become a very polluted package.

Improved documentation would help, I suspect.

 > I won't be able to make it to the Rheinland Zope 3 sprint, but Zope 3 

Neither will I; I'm sur they'll miss us both.  ;-)

 > product development is an area that I'm particularly interested in - 
 > since this is the place where I and so many people will be spending 
 > time with Zope 3.  Regarding packaging, I'd like to encourage  coaching 
 > a hierarchical model, with organizations/projects/companies choosing 
 > their own top level package ('farmdog.bugtracker', 
 > 'roundup.bugtracker') if they have a system of products/packages that 
 > are interrelated.

Sounds like you're volunteering to contribute to the product developer
documentation.  ;-)

 > > I'm happy to add a "path" setting matching this description, however.
 > 
 > That'd be awesome.

Done.


  -Fred

-- 
Fred L. Drake, Jr.  <fred at zope.com>
PythonLabs at Zope Corporation