Do you put in 'copyright' in your code?

I've been seeing 开发者_运维知识库copyright/information about the file/site, and i'm wondering if any of you do it too.

Like in css, before the styling starts.

/* UI: Some Name Designer: Some Name Version: Some Name */

Do you do this with PHP, any other programming language? If so, what kind of information do you put in?

---

Any code you write is automatically covered by UK copyright laws and I beleive the same applies for US copyright law, so it is not strictly necessary.

Some states and countries require it, but they will probably be so distant you would have very little control over the situation if your code was copied.

Remember if you are in employment, any code you write is the property of your employer. Putting a copyright notice in to yourself wont look too good.

If you are putting it in code as you own it, it is only necessary if you expect it to be distributed. No point if it's private!

---

I strongly recommend to always put your name on your work. Unless, of course, you want to stay anonymously because you produce something illegal or in a gray area of legality.

If you want others to be able to reuse your code, that information is needed to have a clear legal state. In addition, you should choose a free license. Also, you should put in your name even if you put your work into the public domain.

If you don't want others to (mis)use your code, the copyright information is even more important, because otherwise you'd have trouble proving your authorship afterwards.

---

Most companies expect something like that in the code not really for copyright purposes, but so that people know who to contact if they are having trouble with the code.

---

It's sensible to let the reader know who owns the code and under what circumstances (if any) the code may be re-used or amended, or simply to say that permission of the author is required. Good software is not ambiguous. A copyright notice in the proper form is part of that.

Also good practice to acknowledge any others who may have contributed code to the work.

Poor man's copyright - I don't think anyone uses that now, there are now some technological solutions to that problem that actually do stand up in a court of law, and include tamper-proof audit trails.