On 7/4/09 7:55 PM, Stephan Richter wrote: > On Saturday 04 July 2009, Christian Theune wrote: >> I took the Zope 3.4 KGS, removed the obvious packages that do not belong >> to the ZTK out of the list and created a home for the master list that >> defines which packages belong to the ZTK. >> >> It's in the Zope toolkit documentation: >> http://docs.zope.org/zopetoolkit/about/packages.html >> >> So, if you see that a package is missing or is classified in the wrong >> way, then please speak up. > > To be honest, I am very disappointed by this list. It is totally meaningless > to me since it does not represent any list with which I can build even a > fairly simple application today. There is not a single z3c package in there.
Maybe not surprisingly I have the opposite feeling. To me, it's already a pretty large set of "definite" packages (~60), and a definitely large set of "definite" + "under review" packages (~120). Are we going to be able to maintain all that software over time? If we do, will we have time to do anything else? To put this comment in perspective, in our consulting engagements, we build applications using "the bicycle repair kit" Tres mentioned somewhere in this thread, plus a few others, totalling usually fewer than 30 packages. The very largest application we've built with Z3-related packages (KARL, ~70K lines of Python) depends on 67 packages which seems like a lot of packages to me. I don't even maintain all of those though. - C _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )