Nicola Ken Barozzi wrote: >>Should the authors (Marc Johnson and Andrew C Oliver I believe are the two >>people of note) of POI get CVS commit rights? >> > > 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. 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). 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. :-) 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). Feedback from the POI devs is most appreciated of course :) Ciao, -- Gianugo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
