How I license code

If you’ve looked at any of my original code lately, you might have noticed how I license it at the top of said code:

# Originally written by Corey Henderson
# Dual-Licensed - you may choose between:
# 1) Public Domain
# 2) WTFPL - see

In a previous post about the GPL, I reference a quote:

Software license synopsis:
EULA: sharing is evil
 BSD: sharing is not evil
 GPL: not sharing is evil

What’s missing from this list is this:

Public Domain: Do what the f*** you want.

I started my career writing GPL code. I was on the “free software” bandwagon not realizing what I was getting into. While the GPL is an excellent license that has done a lot of good for the community at large, it is by no means perfect, and isn’t for everyone. In recent years I’ve started to favor BSD-style license, as more “freedom” is involved, and you still get to keep the credit.

I’m at a point in my life where, for most things I write, I don’t give a flying f*** what the license is. Use the code, claim it as your own, I don’t really care. I wrote it for me, I’m sharing it with the world because it might help someone else out somewhere. I believe in karma, and I don’t want the licensing to be a hurdle for anyone. So I release the code in such a way that anyone can use it and re-use it to their heart’s desire.

Now obviously if I’m working on an already published set of code with its own license, chosen by the author, I have no problem contributing. My tpe-lkm code is GPLv2, and psj is BSD (that’s technically my original code, but my employer at the time didn’t like the idea of it being in the public domain). I’m not going to fret over someone’s choice of license. Unless, of course, it’s an EULA, and they’re not my employer. Your software license is all a matter of personal taste, and if I think I can make a meaningful contribution, I won’t be demanding a change of license conditions.

Now, why dual-license public domain and the WTFPL? Aren’t they the same thing?

Well, not really. The idea of “public domain” varies by country, and our software community is global. So, for the poor blokes who can’t use something in the public domain for whatever reason, I also give them another option they might be able to use. Some may find that license offensive, others funny; either way, it’s my attempt at letting anyone and everyone make use of the code.

Oh and, as usual, no warranty, etc.

Hope you enjoy my no-strings-attached code!

Leave a Reply

Your email address will not be published. Required fields are marked *