Rather than thinking of libraries vs applications, think of various licenses as different tools to achieve different goals. You have first to think what kind of life you'd like to give to your product. E.g.: would you like to create a community? Would you like to have people contributing back code? Would you even enforce them to do that, or only kindly push them to do? Would you allow people making money by incorporating your code in other apps? Make money directly by selling the app? Or would you like to prevent them from doing that, eventually making money out of consultancy? Are you going to use specific algorithms covered by patents?
Only when you've answered to these questions (and even more), you can browse through the list of available FLOSS licenses and choose the one that best fits your needs. PS The "vegan" license is clearly not FLOSS in the strict way. Which doesn't mean it's bad, of course - their own business. I myself I'm writing an application that can be used by birdwatchers and hunters, and I'm evaluating whether I could exclude the latter with a specific license. -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [email protected] - mobile: +39 348.150.6941 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
