cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: [vote] POI commiters (was: RE: [vote] Accepting donated POI serializers/generators)
Date Fri, 11 Jan 2002 12:05:33 GMT
Nicola Ken Barozzi wrote:
> ----- Original Message -----
> From: "Gianugo Rabellino" <>
> To: <>
> Sent: Friday, January 11, 2002 10:09 AM
> Subject: Re: [vote] POI commiters (was: RE: [vote] Accepting donated POI
> serializers/generators)
> > Nicola Ken Barozzi wrote:
> >
> > >
> > > POI development cycle is *very* fast.
> > > I've been working with them for some time, and IMO they should be able
> to
> > > commit on their own.
> > > If they cannot, you will have to deal with loads of daily patches ;-)
> >
> >
> > This kinda worries me. As far as Cocoon is concerned this donation turns
> > out to be a serializer, which most probably (but I haven't seen it yet)
> > should be a little more than a wrapper to some POI driver.
> There is also a new framework that is used to serialize easily file formats
> for POI.
> >  If the API is
> > not stable this might be an issue given that Cocoon is advertised as
> > production-ready and robust (true, we use other unstable and sometimes
> > experimental stuff, Avalon being the most notable example, but this is
> > in a controlled environment).
> To be clear, the *only* contract there is with Cocoon is the configuration
> and the XML input-output.
> The XML format is Gnumeric 1.0, Andy is doing the necessary validation of it
> in unit tests with the schema he wrote.
> Apart from this, Cocoon doesn't care if internal APIs change.
> > Don't get me wrong, I'm really happy about POI being part of the game,
> > but I'd like to have a good reason for having tons of daily patches
> > coming in, or as far as I'm concerned they will be confined to
> > scratchpad for a long time. :-)
> IMHO think it's unfair, given the importance of the project.
> POI is in 1.0 version, I don't think you will want it in scratchpad for
> long, as many users will be asking continuously how to install it.
> My 2cents, of course ;-)
> > In short: I'm absolutely in favor of giving the POI team commit access,
> > but I'd love to see them updating (not too often :)) the poi jars and
> > work on the Cocoon wrappers mostly if not only for bugfixing once they
> > make into production (out from the scratchpad). They should be aware of
> > back compatible issues in case they have to change the API (this is
> > nothing different from the actual situation, I just wanted to make
> > myself clear).
> +1 There are complete unit tests integrated in the ant build, and Gump will
> help guarantee that the contracts are kept.
> The fact is that bugfixes are very very frequent, 'cause we're dealing with
> an undocumented (badly anyway) file format and many M$ product versions.

Easy, Ken.

Gianugo, was simply stating worries about a too-fast release cycle on
the contracts.

But I've asked Andrew that myself and I think the serializer won't
require that many changes so I think everybody is happy.

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche

To unsubscribe, e-mail:
For additional commands, email:

View raw message