Continuing the series of articles about Karl Fogel’s book, now I’m going about a very interest point, and maybe the most important when you decide to release your project under any floss license.
The way to license your software under any floss license follows this:
- You can put in your project webpage the note regarding the FLOSS license you use.
- In the package, you can put a file called COPYING or LICENSE with the text of the full license.
- At last, and the most bored task if you have not done this task while coding your project is put in the headers of every file that is part of your project, a brief note about the license.
The typical note is similar to this (from GNU GPL license):
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>
As you see in the note we put a link to the complete and original text, by the case in that the project doesn’t have the license file.
What does license choose? This topic will be explained in other post, although in previously posts maybe I talked about type of licenses that can give you an idea (maybe the post is in Spanish, I don’t remember sorry, but as I say, I’m going to talk about this soon😉 ).
See you my friends.