+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/ __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
