Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <20030923151107.79382.qmail@web41905.mail.yahoo.com>
Date: Tue, 23 Sep 2003 08:11:07 -0700 (PDT)
From: Timothy Larson <timlarsonwork@yahoo.com>
Subject: Re: on better release and version management
To: dev@cocoon.apache.org
In-Reply-To: <9D2E77F8-EDD2-11D7-B98A-000393D2CB02@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Stefano Mazzocchi <stefano@apache.org> wrote:
...
> I propose a much simpler scheme. A block can be:
> 
>   1) certified
>   2) not certified
> 
> A certified block is said to be guaranteed by the certifier (not only 
> the Apache Cocoon project, but any organization willing to certify 
> their blocks) that this block is usable in production and will be 
> maintained in the future.
...
> certification is meant to guarantee the "backup" of a community or
> company behind the block.
> 
> This allows other entities to do certification (and this would mean 
> that *they* provide support and community/company backup of future 
> development) [if they lie, well, users will know and news will spread], 
> but, more important, it will require a single 'all encompassing' vote 
> from the community which would be: "are we ready to support this from 
> now on?"

And from another Stefano email:
>yes, something like "certified that this is an official cocoon block, 
>it can be used in production and will be supported by the cocoon 
>community in the future"

Beautiful.  Simple administration, good community dynamics designed in,
and a clear way to identify the maintainer, whether it is the Cocoon
community or an external community or company.  I like it very much.

--Tim Larson


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com