Þ   briarpig  » license

open source

     I plan to use my own open source license — mu-babel — on terms suiting myself. My only reason for an open source license is to get a better tipping point for long term viability, so longevity is enhanced by generally open availability. Openness is for software health.

longevity

     Longevity and high availability are my only reasons for open source licensing. There's no moral philosopy, nor any appeal to membership in some ill-defined community. (Appeals to principle pleading causes get this reply: bite me.)

commercial

     Commercial use probably needs terms separate from a non-commercial license. The reason for this is to put teeth into terms, so violation of terms has specific actionable consequences, since nothing else gets respect from business entities. Without this, individuals won't get companies to behave.

money

     Briar Pig has absolutely no problem making a little income (someday) from licensing software. But realistically, it probably won't cover much more than the many nuisance costs associated with running this site and responding to reasonable and appropriate queries. But the real aim of any license model is deterring code forks, with money as incentive. (Cooperation is cheaper.)

scale

     If you want to universally deploy code found here, a commercial license might cost a very small but still nonzero amount. It won't ever be free when you deploy killer apps. If I work for you, I might grant a free, non-exclusive, perpetual license. (This is not an offer to do business.)

moot

     Obviously the whole issue is moot until code shows up for you to use. This is your heads up. The point of this page is to prevent odd assumptions based on expectations primed by what other folks do. Just assume no precedent for a license model.

personal

     Personal use will always be free. You can assume personal use will later always be allowed without fee, oversight, or obligations of any kind. But you cannot publish changes except as permitted by license to be specified later.

sources

     Source code will appear on this site long before you have any license to use it. Publication doesn't mean you have sanction to use or redistribute. It only means I'm happy to show how I do things. My main benefit — in the unlikely event I see any — would be feedback on what you think. I believe you owe me feedback if what you see is interesting enough to hold your attention a while. If you write believing I owe you a favor because you're writing, we'll get off on the wrong foot.

     Choose one of these demos for sample code and related docs, developed together to motivate þ C++ code for this purpose.

     mu: toy, peg, imm, tag, box, symbol, token, number, bigint, class, method, reader, writer, eval, env, vm, gc, world, pcode, compiler, asm, lathe, lisp, smalltalk, design, weight, jar, card, harp, debug, profile

     thorn: todo, names, iovec, assert, log, run, hex, crc, buf, in, out, quote, escape, compare, file, deck, cow, arc, blob, tree, slice, rand, time, stat, heap, node, primes, page, book, pile, stack, atomic, lock, mutex, thread, map, meter, list, iter, ctype

     The new mu menu links future toy language pages. Many demos are stubs; see todo for a thorn demo guide, or toy for mu updates. Also see names for an overview of naming schemes.

• (today) software license: mu-babel
• (always) there's never a warranty
• (always) it's all under copyright

no warranty

     The software is provided "AS IS", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.

images

     Some of the css and many of the images on this site derive from originals found elsewhere: using these shrunken versions is questionable as fair use. The left column's thorny stem looks most like the original and must be replaced someday. (I'll most likely draw a replacement conveying the same thorniness.) The hand images are lightly to heavily edited versions of larger found images. (Besides color and contrast transformations, nearly all of them have labor intensive contour lines added inside and out.)

copyright

     So except for quoted material and images, unless otherwise specified all content on this website — code, documentation, and web pages alike — is copyrighted, with all rights reserved. Permission is only granted to read and store personal copies for future reading use only. You may not redistribute or publish material found here in any form, but you're certainly welcome to make personal copies for later viewing, as long as you don't reprint.