Unfortunately, a lot of us with some experience in IP law, albeit none of us lawyers, believe the additions to the master licence have meaning (else why are they there?), and do have a legal effect on the whole of Shen. See the other discussion I linked to for more, plus discussion on the Shen mailing list.

Maybe we're wrong, and you and Tarver are right, but as long as this is a debatable point most if not nearly all of the value of re-licencing has been negated.

> Maybe we're wrong, and you and Tarver are right, but as long as this is a debatable point most if not nearly all of the value of re-licencing has been negated.

I agree with your point. I think it's BSD, you think it's modified BSD. Who is right or not, it's up to lawyers to decide, and this is the exact reason why people wanted standard license for Shen, to avoid the confusion.

However, it's closer to standard license than previous, and I'll take the risk to use it for my personal projects, but I won't bother using it at work for anything, since I know my employer will not pay the lawyers to review it.

What's your opinion on using it for "serious" (i.e. things that might be used by others) open source projects? Say, using Shen as part of the toolbox of an operating system, as Barrelfish uses Haskell (http://www.barrelfish.org/ i.e. the Mackerel DSL to describe system details and the Hake build system).

This is not an idle question, BTW. I'd personally like to do something like Barrelfish and/or a "21st Century Lisp Machine" sort of system, having been part of the 20th Century Lisp Machine community in the early '80s. And my reaction to Haskell's syntax is akin to a lot of people's reactions to Lots of Irritating Sets of Parenthesis.

But Haskell has a very serious community, Shen doesn't, and I strongly suspect it never will.