New Year, New License

Posted on January 02, 2005  |  

Posted in Apologetics


Having read John’s comments on the Markdown licensing I decided to change my own licensing too. I publish quite a bit of code here and have no illusions of becoming “rich and famous” doing it, so why prevent its use in grass-roots and commercial projects alike? I’m going with the BSD license which, although very liberal, still is a license, so please take a minute and read it.

In layman’s terms, it’s a free-for-all kind of thing, but donations are still much appreciated.

This is going to be an exciting and productive year in terms of coding and design projects, so stay tuned!


on May 1, 2005

Markdown seems like a very intutive input solution. I created a simple interface for my customers a couple years ago but not nearly as rich as Markdown. I'm considering "upgrading" the interface to Markdown as a standard of sorts, but I'm not sure how to correctly site the author.

If I use your Markdown.Net dll for commercial purposes, would I need to put a link on every page stating "this is licensed via BSD license"? Even those pages that don't implement Markdown [ie no input textarea]? Would the link text need to be identical to your license text? How would it / could it be altered?

Milan Negovan
on May 1, 2005

Carl, I believe you have to drag the license file around only if you modify and redistribute the code.

If you simply bake it into a product (commercial or non-commercial alike), you don't need to list the fact that a third-party component was included with a BSD license, and so forth.

The reason I chose BSD is because I wanted to avoid any and all complications for others. :)

on May 2, 2005

Great! I was prepared to create my own Markdown from scratch if I needed to. It would have been a nice exercise in regular expression processing, no doubt, but I'll opt for the drop-in dll. That certainly avoids complications. Thanks.