[Zope2-migration] New mailing list

[Steve Alexander]

I'm going to play devil's advocate in this email. Don't take my 
questions to imply my real opinions and needs wrt zope2 migration.


> But there is still a co-dependency between the two groups:

> Zope 3 implementors desperately need people to write applications for
> Zope 3, particularly in advance of the Zope 3 launch.  (Launching
> with zero usable products will be pretty bad.)

Why should that bother someone who is developing Zope 3 and intends
using it for their own in-house purposes?


> Zope 3 implementors also need more people participating in
> implementing, so they need companies to support the effort and
> contribute staff time.

True. There are more ways to contribute than writing code.


> Zope 3 deployers need an architecture that will last at least 3
> years, and they need it to arrive pretty quickly.

There won't be any Zope 3 deployers until Zope 3 arrives. I don't see
how they need it to arrive quickly.


> I'm not sure how this symbiotic practice works in practice, though.
>  Obviously zope3-dev and #zope3-dev aren't ideal for discussions 
> attractive to deployers.  I don't have any good suggestions on how 
> deployers can influence implementation, unless they become
> implementors.

Deployers can start writing a non-critical application.

* For the deployer, this increases their knowledge of zope 3.

* For the implementors, this motivates work and design choices that
   are informed by the needs of deployers.

And, if the non-critical application is made openly available

* Others can learn from the application, and build on it.

--
Steve Alexander