Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 56320 invoked by uid 500); 16 Jan 2003 11:26:13 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56302 invoked from network); 16 Jan 2003 11:26:13 -0000 Message-ID: <3E2696DE.90508@apache.org> Date: Thu, 16 Jan 2003 12:26:22 +0100 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [VOTE] Inclusion of SAP R/3 components References: <20030115133254.GA1341@bremen.dvs1.informatik.tu-darmstadt.de> <3E2568EC.80007@outerthought.org> <3E267554.4080101@anyware-tech.com> <20030116093834.GC1341@bremen.dvs1.informatik.tu-darmstadt.de> <3E268609.3030206@anyware-tech.com> In-Reply-To: <3E268609.3030206@anyware-tech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: [...] > What I said is that code becomes zombie if it's not included in the > distro of the source base that _contains_ the code. > > Visibility is another problem, and this is chicken and egg : cocoon-apps > will be visible if it contains substantial material, and substantial > material will come in only if cocoon-apps is visible... (same applies to > cocoondev.org) Cocoon-apps has been created in overlap with cocoon-dev, and to get stuff from Andy, CocoBlog and Wyona. Andy didn't finish it, CocoBlog is lingering between that and Cocoondev and Wyona... well, it will probably be a project itself. So cocoon-apps is empty now and I don't see it become less-empty soon. Overmore there is cocoondev which is already active. Yes, it would be nice not to need to keep all blocks in the Cocoon CVS repo, but move them *again*? And which? When we'll move to Subversion, dir moves will be possible, and then we'll be able to make these decisions without technological problems. > Also, we have to consider the size of these components : the Cocoon core > provides so highlevel and powerful abstractions that adding a > substantial amount of functionnality in a very specific area requires > only a few classes. Do 10 classes require a separate project/module ? > But they clearly don't belong to the core. So what ? If it's not in the core it's a block, even if only one class. > I'm puzzled... (hence the -0.5) > > Sylvain > -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org