Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 34920 invoked by uid 500); 14 May 2003 01:11:12 -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 34904 invoked from network); 14 May 2003 01:11:12 -0000 Received: from unknown (HELO set.superlinksoftware.com) (66.35.175.110) by daedalus.apache.org with SMTP; 14 May 2003 01:11:12 -0000 Received: from dhcp216-12-226-137.ohr.dal.wayport.net ([216.12.226.137]) by set.superlinksoftware.com (JAMES SMTP Server 2.1) with SMTP ID 254; Tue, 13 May 2003 21:00:49 -0400 (EDT) User-Agent: Microsoft-Entourage/10.1.0.2006 Date: Tue, 13 May 2003 20:11:20 -0500 Subject: [VOTE] Move cocoon-poi-block stuff to POI From: "Andrew C. Oliver" To: POI Developers List , Stefano Mazzocchi CC: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Cocoon folks please vote: [ ] +1 [ ] +0 [ ] -0 [ ] -1 POI Folks please vote on accepting this: [ ] +1 [ ] +0 [ ] -0 [ ] -1 For explanations read below. I'm too tired to recite it all and be fancy. -Andy On 5/13/03 12:54 PM, "Stefano Mazzocchi" wrote: > on 5/13/03 7:04 AM Andrew C. Oliver wrote: > >> Hi, >> >> How would you guys feel about giving all POI committers CVS access to the >> HSSF Serializer block? >> >> The only downside may be granularity of CVS control, but that could be >> gotten around by saying "don't commit outside of the block" to the >> committers who are all reasonable nice guys. >> >> The advantage: While I hope around the world, they will have the ability to >> fix these kinds of things. >> >> Alternatively, I'm game to see it moved to the POI module and genericized to >> be non-cocoon specific. >> >> Thoughts? (both lists) > > I'd be in favor of moving that code to POI. Nobody else uses it and we > don't know how to manage/fix it. > > I strongly believe code should reside where there is a community that > maintains it, not where it makes more sense architecturally. > > But sometimes I don't find other people resonating with this vision so > count this as only my personal opinion. -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI?