Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 91128 invoked from network); 28 Aug 2008 06:56:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Aug 2008 06:56:41 -0000 Received: (qmail 18360 invoked by uid 500); 28 Aug 2008 06:56:38 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 18326 invoked by uid 500); 28 Aug 2008 06:56:38 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 18315 invoked by uid 99); 28 Aug 2008 06:56:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Aug 2008 23:56:38 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [195.242.168.1] (HELO mgate.ops.co.at) (195.242.168.1) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Aug 2008 06:55:41 +0000 Received: from smtp.ops.co.at (smtp.int.ops.co.at [172.27.0.4]) by mgate.ops.co.at (OPS Mail Gateway - authorized use only - NO UCE/UBE C=AT L=VIE) with ESMTP id 139D7AFE51 for ; Thu, 28 Aug 2008 08:56:09 +0200 (CEST) Received: by smtp.ops.co.at (Postfix, from userid 65534) id 0520A6E023F; Thu, 28 Aug 2008 08:56:09 +0200 (CEST) Received: from [172.27.1.104] (lints2.int.ops.co.at [172.27.1.104]) by smtp.ops.co.at (Postfix) with ESMTP id 08D3F6E0234 for ; Thu, 28 Aug 2008 08:56:08 +0200 (CEST) Message-ID: <48B64C07.5060106@apache.org> Date: Thu, 28 Aug 2008 08:56:07 +0200 From: Simon Kitching User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: MyFaces Development Subject: JSF2.0 implementation Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on smtp.ops.co.at X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, hits=-4.3 required=7.0 tests=AWL,BAYES_00,RATWR10_MESSID, SPG_MG_XXXMD2,TW_JS autolearn=no version=2.64 I see from the commit list that a new JSF2.0 branch has been created. I don't remember seeing *any* kind of discussion or even announcement about this. While I am happy to see JSF2.0 work going on, this kind of approach does not seem to be at all in the "community" spirit. IMO, major events like this should be discussed beforehand. One issue, for example, is that the core-1.2 stuff is currently half-way-converted from the trinidad plugins to the myfaces-builder-plugin. So now it is branched, any changes need to be applied in two places. In addition, a large amount of code has just been committed by someone (slessard) who is not a particularly regular contributor to myfaces. Where did this code come from? Do we need a code grant for it? Note that when code is developed iteratively on the dev list then there is no need for a grant. But a sudden code dump is different, even when contributed by someone who has signed a CLA. And with 3 branches to now maintain, we need to discuss whether and when we phase out maintenance of the jsf-1.1 branch. Currently when users provide patches in jira, they almost always provide a patch against only one version and the committer ports it, which does increase the load on existing committers. When do we stop asking committers to do this when patching bugs? To repeat, I'm *happy* that jsf2.0 implementation is in progress, and appreciate people contributing time to write an ASF-2.0-licensed implementation. But it is a standard saying at Apache that "community is more important than code", and the "community" aspect here seems to have been rather neglected... Regards, Simon