[Zope3-dev] Mail delivery failed: returning message to sender

[Mail Delivery System]

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  corey at streamreel.net
    SMTP error from remote mailer after RCPT TO:<corey at streamreel.net>:
    host iris1.directnic.com [204.251.10.81]: 550 5.7.1 No such recipient

------ This is a copy of the message, including all the headers. ------

Return-path: <zope3-dev at zope.org>
Received: from cache1.zope.org ([12.155.117.38])
	by mail.python.org with esmtp (Exim 4.22)
	id 1Aqski-0006Zj-Mj; Wed, 11 Feb 2004 06:42:00 -0500
From: zope3-dev at zope.org (philikon)
Reply-To: zope3-dev at zope.org
To: ;
Subject: [PackageGeddon] (new) 
Message-ID: <20040211064200EST at dev.zope.org>
X-BeenThere: zope3-dev at zope.org
X-Zwiki-Version: 0.21.1
Precedence: bulk
List-Id:  <zope3-dev at zope.org>
List-Post: <mailto:zope3-dev at zope.org>
List-Subscribe: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/PackageGeddon/subscribeform>
List-Unsubscribe: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/PackageGeddon/subscribeform>
List-Archive: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/PackageGeddon>
List-Help: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture>
Date: Wed, 11 Feb 2004 06:42:00 -0500
X-Spam-Status: OK (default 0.000)

PacakgeGeddon

  Author

    Philipp von Weitershausen (philiKON)

  Status

    IsProposal

  Problem

    'zope.app' contains much functionality, too much really. It
    contains many things that are going to be customized by
    applications later, like the browser skins and the content
    components.

    We have decided that the place for everything that is
 
      a) optional in some sense or

      b) going to be customized once or more

    is 'zope.products'.

  Proposal

    The following packages shall be moved:

      - 'zope.app.content' (and its interfaces, browser views) will
      become

        * 'zope.products.folder' (note that the folder component
          itself cannot be moved out because of dependencies; this
          package will only contain its browser views and
          configuration).

        * 'zope.products.file'

        * 'zope.products.image'

        * 'zope.products.i18nfile'

        * 'zope.products.i18nimage'

        * 'zope.products.zptpage'

        * 'zope.products.dtmlpage'

        * 'zope.products.sqlscript'

      - 'zope.app.workflow' (and its interfaces, browser views ) will
      become 'zope.products.workflow'

     - 'zope.app.browser.skin.rotterdam' will become 'zope.products.rotterdam'

     - 'zope.app.browser.skin.zopetop' will become 'zope.products.zopetop'

     - 'zope.app.onlinehelp' (and its interfaces, browser views) will
     become 'zope.products.onlinehelp'.

  Discussion

    Most of the discussion has already been held in the "'Moving more
    stuff to zope.products' thread on the zope-dev
    list":http://mail.zope.org/pipermail/zope3-dev/2004-February/009543.html

    Here's a short summary:

      - the change will make zope.app smaller and easier to maintain

      - it will flatten the hierarchy (no more searching in
      zope.app.interfaces, zope.app.browser for packages that really
      belong together, like workflow).

      - it will show developers what is supposed to be customized and
      what they actually *can* customize easily.

      - it will put certain packages, like the browser skins, in the
      hands of specific maintainers. This will hopefully improve the
      maintainance on these packages.

  Implementation

    This proposal is currently being implemented in the
    'philikon-movecontent-branch'.

--
forwarded from http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/PackageGeddon