Two reasons specifically: first, I wanted to avoid a fork/split of the project, therefore it does not allow redistribution of the software. I prefer to keep the community together. Second, as a Christian I had ethical concerns about the use of this software for immoral purposes. Neither of these can be prevented by the standard MIT or GPL license.
There's also the possibility someone may want to purchase BoltWire for a million bucks, and I could buy a home in the country and retire. Not likely, but hey, you never know. :) Cheers Dan On Fri, Dec 25, 2009 at 5:43 AM, Erlend Sogge Heggen <[email protected]> wrote: > May I ask, what made you choose to make a custom license? Standard > licenses such as MIT or GPL tend to protect your product more > carefully, as they have been tested through time. It is also easier to > know whether or not they are compatible with other licenses. It sounds > to me like you want for your product pretty much what the GPL offers. > Why make it harder on the end-user by introducing another foreign > license into the open source mix? > > -- > > You received this message because you are subscribed to the Google Groups > "BoltWire" 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/boltwire?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en.
