Zope 3 wiki → Developer Info → Proposals →
last edited 4 months ago by simon
created: 2004-06-14

DraftProposals

Some works in progress:

  • One namespace for ZCML

    (Basically) get rid of ZCML namespaces, consolidating all ZCML directives into one namespace.

  • Page Architecture

    An architecture for assembling pages from parts, such as pagelets and portlets.

  • Specification Unification

    Unify interfaces with the specification of attributes (e.g. fields) for objects providing the interfaces.

  • Method specification

    Provide richer specification of method parameters

  • Access to widget errors

    Add API for getting and setting errors on widgets.

  • Site Themes

    A simple way to apply corporate identity to all pages in a site without touching the Dreamweaver person's HTML.

  • File-system resources

    Improving file-system resource publishing, allowing greater flexibility.

Here is a ProposalTemplate for creating new proposals.


comments:

... --PjotrPrins?, Mon, 18 Dec 2006 12:01:55 -0800 reply
I think we should remove the proposals (draft or not) from this Wiki. Many a time searches and queries lead to these pages and it is never really clear what is implemented (already) and what not. It confuses new comers and people trying to find their way. Just try searching for user management, right now in this Wiki.

I understand the need for a platform for architectural changes and their proposals, but I think it hurts ZOPE that it mixes with general documentation.

How about moving proposals behind a password - so they don't come up in searches anymore. I guess it is a small crowd that is interested anyway - and in my humble opinion ZOPE3 is quite good as it is and amendments are really about components and belong with a component - not with mainstream ZOPE.

... --Christian Theune, Mon, 18 Dec 2006 23:10:56 -0800 reply
I don't think so. The Zope 3 wiki was built up as, and still is, a resource for the development of Zope 3. We shouldn't mix that with communicating about Zope 3. I think we should make it clear which proposals are in which status, maybe using a table like the PEPs? do.

... --SteveAlexander?, Tue, 19 Dec 2006 01:28:25 -0800 reply
Actually, I suggested a while back to use Launchpad to track the status of proposals. This kind of thing has been very successful for the Ubuntu project. Here's the Zope3 proposals imported into a demonstration version of Launchpad.

https://features.demo.launchpad.net/products/zope/+specs

... --simon, Wed, 16 Apr 2008 17:44:19 +0000 reply
As part of proposals cleanup, I made a dynamic page intended to replace the manually-maintained Proposals and OldProposalsList. See http://wiki.zope.org/zope3/AutomaticProposals . Comments ?

... --simon, Fri, 18 Apr 2008 00:03:08 +0000 reply
Proposals now shows comment counts and status based on the RST :status: tag. Stephan points out that there is useful status info on OldProposalsList which should be merged into the proposals, so that content will stick around until that happens. Summaries are the initial proposal text (consistency here would allow nicer summaries).

You lose something when you move away from a dirt-simple editable page of links, but I think here the automation is worth it. So with two for and none against, in it goes.



( 96 subscribers )