I'm not all that in to law and things like that. Just for understanding, if you have a program p and a license l all you have to do is state that the program is under that license in the source to put it under that license, right?
Also, how smart would it be to write a custom license for your OS if you intend for it to be closed source?
Licenses
-
crazygray1
- Member
- Posts: 168
- Joined: Thu Nov 22, 2007 7:18 pm
- Location: USA,Hawaii,Honolulu(Seriously)
Licenses
Codname: Cipher
Working On: Design Doc(CFFS file system)
Working On: Design Doc(CFFS file system)
Re: Licenses
To note, I am not a lawyer.crazygray1 wrote:I'm not all that in to law and things like that. Just for understanding, if you have a program p and a license l all you have to do is state that the program is under that license in the source to put it under that license, right?
Also, how smart would it be to write a custom license for your OS if you intend for it to be closed source?
Usually a header or the like is used. Other times a 'LICENSE' file is simply placed in the root directory. I'm not sure which is more legally secure, but to be safe, I'd include a header.
Writing a custom license is, IMHO, a bad idea, especially if you aren't familiar with copyright law. I would get a real lawyer to write something up if I needed such a license.
C8H10N4O2 | #446691 | Trust the nodes.