Pier Fumagalli wrote: <snip/> > > All they asked me for for is some form of "recognition" if the code > ends up in Cocoon land (quick quick, go back and modify the @author > fields in the classes to include VNU Publications), so that they can > prepare a nice "press release" to please our investors, and they can > have better discounts when asking for something to be developed by > Orixo :-) (hi guys! :-P)
Just like anybody else that contributes, the status.xml file (i.e. Changes) and the CREDITS.txt provide plenty of exposure. Documentation and examples of use could provide even more. > My _personal_ requirement, is that I wouldn't want a clean-cut fork to > happen, because at the end of the day, I'd have to abandon the Cocoon > fork and get back to the VNU's fork (doh, they pay me). > > A directory on the CVS repository which I can check out and build > without requiring too many dependancies on Cocoon's main "publication > core" will be more than enough, I can build my own "Ant" build files. > That would make my (working) life _so_ much easier... You could just add it to cocoon-2.2 and do whatever you want. --David
