!rant

<title>
Release "Unlicensed" to avoid problems
<\title>

I have done some work as intern I have done some work. I didn't have a contract though and one month ago I wanted to go away to give more time to my studies.

Now they ask me to write a brief documentation to explain how to use what I have done.

Since I have no hope to receive money and I just want to make sure they don't come back asking me things or blaming me about the implementation I thought to release with "The Unlicense" license...

What do you think?

If they promised to pay and are not going to, I would say screw them and no documentation. Otherwise, I would go for GPL, so if they work on it, you can get at least the result back. Public Domain is noble idea but companies love it because they can get stuff for free and sell it to others.

@miska
Thanks for the reply

But I fear that it won't go well, that what I have written is not good enough... I wrote some server side payment validation functions that were never tested (as the whole project).
There is a little possibility that that work out... But I just want to be sure that I won't be liable for that

Well, blamed and liable are two different things. Not a layer but my guess would be no contract = no guarantees ~ no liability. Licensing when you are contributing to existing project might be tricky as you are at least partially bind by the project license. You can play nice if you are looking to score a job with them later on, but if they just used you I wouldn't feel much obligations. Although if you are just starting might be nice warm feeling to know that your code is oit there powering something... You have to decide how much more effort is that feeling worth.