Hi:
As the author of the Wildebeest License, I can explain the inspiration behind
it. I live in England, and Licenses formulated for US Law are kind of illegal
here. The No Warranty Express Or Implied stuff is apparently intended to
satisfy the Uniform Commercial Code covering sales of goods
I would add-
Some strange license? Ditch it, we
are not going to take chances. - Voice of
Responsible (TM) corporate management.
Seriously, why they should pay for
legal expertise and still would not be
sure of (practical) consequences?
Popular/known licenses are hard enough...
And if
Late for the show but not the party!
On Fri, Jun 01, 2012 at 04:07:58PM -0700, Jakub Lach wrote:
I would add-
Some strange license? Ditch it, we
are not going to take chances. - Voice of
Responsible (TM) corporate management.
Seriously, why they should pay for
legal expertise and
Sorry, should have written more about
ants to keep you happy.
(As a matter of fact, indeed I didn't register date
of previous posts, not a lot going through list it
appears.)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/BSD-license-tp5632493p5714097.html
Sent from the
Frank Mitchell mitch...@wyatt672earp.force9.co.uk writes:
Hi: Why not write your own Software License? Just avoid anything
illegal.
Because
1) Unless you are an IP lawyer yourself, you are very likely to end up
with something that is either ambiguous, full of loopholes, or
unenforceable.
Hi: Why not write your own Software License? Just avoid anything illegal.
Before composing the Wildebeest Licence I read some legal stuff to ensure it
made sense. Remember, I live in England, where Copyright Law is different, and
licenses formulated for the USA can be silly. Microsoft's
