Hello, * 2009-08-06 17:03, Tres Seaver wrote:
How about another one:
* the package has to be usable with all of Zope 2, grok and the Zope 3 application server
That guarantees the stated goal that ZTK is reusable.
I would restrict it to the "big toolkit" set which is "used by" those three, rather than "usable with" them. Packages which aren't actually used by those frameworks are objectively less well supported, even if some developers use them for some apps built on top of the frameworks.
Am I correct saying that your idea is to restrict the ZTK to the packages defined as the intersection of the dependencies of zope2, zope3 and grok? ZTK = intersection ( zope2-dependencies , zope3-dependencies, grok ) I don't think this definition fits our needs, but my skills on gron and zope2 are too limited to bring counterexamples. -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564