Am Mittwoch 04 März 2009 18:03:17 schrieb Lennart Regebro:
> On Wed, Mar 4, 2009 at 17:48, Martijn Faassen <> 
> > Note that the Zope Steering group is not about
> > packages that are not in the framework, so if lovely.remotetask isn't
> > there, it can say little.
> Which is exactly my point. It surely isn't at the moment, and I don't
> see that it should be any time soon. What Hermann suggested is
> somebody that keeps track of all Zope software modules and tells him
> which is good and which is bad. That's not what you suggested, and as
> mention, I don't think it's even possible, and definitely not a good
> idea.

Well, yes and no: My idea is that there will be a well-defined set of core 
packages, and probably some extra packages that are also embraced (e.g. maybe 
z3c packages, e.g. z3c.form).

Of course, trying to embrace every zope package out there will not work. But I 
think it will make sense to embrace packages that cover a common usecase, for 
instance, creating remote tasks is nothing uncommon and will be needed by 
many people. Therefore I'd suggest to embrace at least one package that 
covers that functionality (e.g. lovely.remotetaks, or zc.async, or something 

For all other packages, it will make sense to create some infrastructure, as 
stated in another mail of Martijn.

Best Regards,

GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7
Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to