I think that for the purpose of the javaposse podcast in most cases it's not important what the license is. They could divide it into simplistic piles like 'open source' or 'commercial' and that would be good enough most of the time.
There are times when the license is important vital to a specific project. It's most especially true when it's time to incorporate an external project into an app you're writing because of license compatibility issues. Sometimes I expect the license to be worthy discussion on the javaposse but most of the time it should be ignored. ...on...the...other...hand... after reading some of the responses below there is one thought in my mind. I prefer open source licenses and don't like the times when I've heard a glowing recommendation of some product, rush over to the web site, am excitedly reading about it, then crushed when I learn it's a closed source $$$ license which I can't afford and cannot use. I'd like to know at the outset if it's open source or not to avoid having to spend that time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
