Siddhartha P. Chandurkar wrote: > actually, i would like to know the details about licensing.Whether i should > use Apache Style License or GNU. What is the procedure for licensing. What > are the things one should take care when releasing an Open Source Product.
There is nothing that we can really say to that. It is a case of deciding what is best for you and your company. Which set of community values to want associated with the source. Ones that surround a BSD-style license are very different to those that surround GPL code. What other companies can do with your code is another factor. Do you want anyone to just take, modify and turn into their own proprietary product or do you want everyone forced to contribute back to the global pool? These are only decisions you can make based on what you think is commercially acceptable to yourself and your company. As a company, my company (Yumetech) prefers to LGPL license all our open source code, where other companies prefer Apache/BSD/public domain or any number of other licenses. We have our reasons for prefering LGPL, but they are probably not the same ones that you will have. -- Justin Couch http://www.vlc.com.au/~justin/ Java Architect & Bit Twiddler http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
