[Zope-dev] Dependencies and future of zope 3

[David Pratt]

Hey Roger. Sounds reasonable to me. Can we also discuss the potential
of only including testing setup for dev eggs and removing testing as
part of a release when the eggs are packaged to pypi or other
repository for consumption.

Besides loosing the dependency, this makes for happier folks external
to zope that consume our eggs.

While I personally do not like the contributor agreement, I am willing
to sign to help out to work with you and others to get this settled. I
am busy just like anyone else, but this stuff with the dependencies
has to end now. Weve been with eggs for more than a couple years,
progress has been made but it has been slow. Seriously, let's see what
we can do to.

The browser packages are a good place to start. Testing another. Third
would be seriously examining dependencies of core again once this is
done. Fourth might be tackling some of the zope.xxx zope.app.xxx
relationships. Some of the stale packages in the main repository and
placing them at another location if they are unmaintained might also
be in order.

If we want to folks to use zope we need to be friendly to wsgi with or
without a zodb and show both sides of the coin - that CA + choice of
backend + zope security + choice of traversal method (with publisher)
== interesting, productive, mature, dynamic and efficient.

On Wed, Sep 3, 2008 at 3:06 PM, Roger Ineichen <dev at projekt01.ch> wrote:
> Hi
>
>> Betreff: Re: [Zope-dev] Dependencies and future of zope 3
>>
>> On Wed, Sep 3, 2008 at 11:41 AM, Stephan Richter
>> <srichter at cosmos.phy.tufts.edu> wrote:
>>
>> > For several packages we took the following approach. Most packages
>> > that have browser packages are in zope.app; for example,
>> > zope.app.folder (we did not convert this package yet). We
>> then took the API and moved it to zope.folder.
>>
>> Maybe we should create a new namespace package for "browser" code.
>>
>> How about "zope.browser"?
>
> Most packages which are interesting for reuse
> provide more or less only ZMI related views.
>
> What about zope.zmi if they provide views for
> the ZMI. This views are allmost unuseable
> outside the ZMI (know as Rotterdam skin)
>
> Regards
> Roger Ineichen
>
>> --
>> Benji York
>> Senior Software Engineer
>> Zope Corporation
>> _______________________________________________
>> Zope-Dev maillist  -  Zope-Dev at 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 )
>>
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev at 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 )
>