From: Francesco M. <f18...@ya...> - 2005-07-26 14:29:50
|
Hi, > I think Ryan's idea is best, they can dual licence it if they like, > but one of them has to the wxWindows license. As he pointed out, I > completely missed the ramifications of the BSD license clause and I'm > sure it can get much uglier than that. I've seen quite a few licenses > with catches like, "for commercial use you must merely contact me...". > What if you're not around anymore? The more I think about it, we > should be fairly strict about licensing since it'll only cause > problems later. > > How about the wording below, I think we need a compelling explanation > why we want the wxWindows license and a note about 3rd party libs > since it's bound to come up as a question eventually. > > "Each component must be made available under the wxWindows license. > This is to ensure that there will be no misunderstandings by users of > your code or clashes between components that may rely on each other. > Remember; this code repository is designed to facilitate code reuse. > Small third party libraries that you may include or link with your > component will (of course) maintain their original license and you > should note that in your documentation." ok, that's still okay for me... Francesco |