Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 5903 invoked from network); 15 Mar 2006 15:11:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Mar 2006 15:11:23 -0000 Received: (qmail 32151 invoked by uid 500); 15 Mar 2006 15:11:14 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 32078 invoked by uid 500); 15 Mar 2006 15:11:13 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 32066 invoked by uid 99); 15 Mar 2006 15:11:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Mar 2006 07:11:13 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.111.4.28] (HELO out4.smtp.messagingengine.com) (66.111.4.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Mar 2006 07:11:12 -0800 Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 6E6D0D403DE for ; Wed, 15 Mar 2006 10:10:51 -0500 (EST) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend1.internal (MEProxy); Wed, 15 Mar 2006 10:10:51 -0500 X-Sasl-enc: e2YT/B6z2VxcpLcVlZSEwVFOSo9mX7ga+2ArTTGgoJ5P 1142435447 Received: from [10.0.0.3] (host-87-74-127-123.bulldogdsl.com [87.74.127.123]) by www.fastmail.fm (Postfix) with ESMTP id 2A3616CC for ; Wed, 15 Mar 2006 10:10:47 -0500 (EST) Message-ID: <44182E79.1010701@odoko.co.uk> Date: Wed, 15 Mar 2006 15:10:49 +0000 From: Upayavira Organization: Odoko Ltd User-Agent: Mail/News 1.5 (X11/20060213) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] OSGi based blocks References: <44173F14.4030701@nada.kth.se> <441826A6.7070900@dslextreme.com> <441829E3.8040409@odoko.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Peter Hunsberger wrote: > On 3/15/06, Upayavira wrote: >> Personally, the long waiting for this blocks system is having very >> unfortunate effects on our community. We need to change that. Take the >> development of blocks off the front stage, and let it happen quietly >> somewhere until there's something clear for us to see and play with, >> rather than preventing people from being able to innovate because they >> can't understand the status of trunk and don't have time/resources to >> invest in working it out and keeping up. >> >> That means that all that are left are those of us that have 'personal >> spare time'. The rest of us, who do all of our Cocoon work as a part of >> our livelihoods, can't find time to contribute to Cocoon because we >> can't justify it - it is just too hard to work out where to contribute. >> >> And 'just waiting' is dangerous, as each moment some of our valuable >> resource wanders away. > > Do that, and nothing other than 2.1 will ever happen. Getting real > blocks is a big thing. It looks like a lot of work, everyone has > always known that. Now that there is a little bit of momentum in the > blocks direction is no time to kill it. I never said 'kill it'. I said 'move it'. I very much value the blocks work, but at the same time I think it is stifling the rest of Cocoon. I would like to see blocks and Cocoon 2.1.X move along in parallel, and as soon as blocks are sufficiently mature and stable, they merge. The current state of affairs with a tiny minority working on blocks (however cool) and nothing else happening is far from healthy. Upayavira