Mark committed his work in the internal HP CVS tree I used to maintain for my own development. I now need to create a patch and apply it to the main Cocoon tree, but unfortunately the amount of changes that happened in between is quite substantial. I'll try to come up with a patch late this week/early next week.
Regards, Ovidiu On Tue, 1 Jan 2002 07:18:54 -0800 (PST), Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Mark, > Any news that you can share on the status? Is there anything we can do to speed up >the process? > > Thanks, > dims > > > I'm not sure how Mark manages the source code. However irrespective of > > that I think it's a major hassle to work with HP IT to have a > > read-only CVS on an external machine, and manage the CVS repository > > updates from an internal site. But the situation may be better in UK; > > any thoughts on this, Mark? > > > > Ovidiu > > > > On Sat, 17 Nov 2001 17:52:33 -0800 (PST), Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > > > Ovidiu, Mark, > > > > > > One request, can you make sure that the latest DELI code is available using >anoncvs to anyone > > > interested? > > > > > > Thanks, > > > dims > > > > > > --- Ovidiu Predescu <[EMAIL PROTECTED]> wrote: > > > > After some discussion with Mark on this, we decided to go with #1, > > > > which I think is the best way to approach this short term. We start > > > > doing some work in this area and put it in the scratchpad area for > > > > people to look at it. > > > > > > > > Thanks Stefano and Dims for all the suggestions and ideas. > > > > > > > > Best regards, > > > > -- > > > > Ovidiu Predescu <[EMAIL PROTECTED]> > > > > http://orion.nsr.hp.com/ (inside HP's firewall only) > > > > http://sourceforge.net/users/ovidiu/ (my SourceForge page) > > > > http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) > > > > > > > > > > > > On Wed, 14 Nov 2001 05:17:17 -0800 (PST), Davanum Srinivas <[EMAIL PROTECTED]> >wrote: > > > > > > > > > +1 for #1 below: This is the quickest and easiest way. As we go > > > > > along we can reconsider the options. One problem i see with #1 is > > > > > that if Cocoon Committers find bugs in DELI code, how quick can the > > > > > turn around time be to fix it? (Since Cocoon Committers would not > > > > > have commit privileges? ) > > > > > > > > > > Thanks, > > > > > dims > > > > > > > > > > > I see two possible way to collaborate: > > > > > > 1) you write the glue code to DELI, we include it and DELI as a > > > > > > library. You keep the stuff at HP, we get the functionality and you get > > > > > > the visibility. > > > > > > 2) you donate the DELI code to us and become an active developer of > > > > > > this list to continue to improve on it. > > > > > > > > > > > > IMO, at this very moment, option 1) is the simplest for all of us since > > > > > > the important part, for me, is not the code, but the fact that we work > > > > > > together. And this is achieved in both choices. > > > > > > > > > > > > So, we just need to find the easiest entry path and 1) is probably the > > > > > > best. > > > > > > > > > > > > > > > ===== > > > > > Davanum Srinivas - http://jguru.com/dims/ > > > ===== > Davanum Srinivas - http://jguru.com/dims/ > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
