cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject [VOTE] Move cocoon-poi-block stuff to POI
Date Wed, 14 May 2003 01:11:20 GMT
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" <stefano@apache.org> 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?


Mime
View raw message