GSmartControl License

This product is multi-licensed under GNU GPL versions 2 and 3. You are free to choose which one you use.

This program is free software: you can redistribute it and/or modify it under the terms of either version 2 or (at your option) version 3 of the GNU General Public License as published by the Free Software Foundation.

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 Licenses for more details.

You should have received copies of these licenses along with this program. If not, see http://www.gnu.org/licenses/.

See GNU GPL version 2 and GNU GPL version 3 for details.

Additional information is supplied with the product. See LICENSE_gsmartcontrol.txt file.

License and Copyright

You may notice that GSmartControl is not licensed under "GNU GPL version X or later", but under "GNU GPL version X and Y". I firmly believe that it's unwise to license a piece of code under non-existent licenses, whatever anyone else might say. The reason for this is that one simply CANNOT know that, say, in 20 years FSF won't be bought by some corporation who will release GPL version Z which will completely reverse the reasons GPL was created for.

The removal of "or later" clause somewhat imposes responsibility on the copyright holders to review every future version of the license once it's released, and, if deemed acceptable, re-license the code under the new license (possibly retaining the old licenses). Unfortunately, this is a necessary inconvenience we will have to deal with.

Patch Licensing

Due to reasons described in "License and Copyright" section, to make it possible to re-license the code without tracking down all the people who ever wrote a patch, the copyrights of all minor patches must be assigned to the central copyright holder of the project. If the patch is major enough (that is, it forms a significant part of the program source code), the author may retain the copyright, if he or she chooses to do so. However, unless the author plans to maintain his part of the source code, he / she is humbly asked to consider assigning away his / her copyright. A simple "I disclaim all copyright to this patch" by the author is sufficient. All credits will be mentioned in product documentation, whatever the size of the patch is.

Please note that centralization of copyright is needed to maintain a reasonably healthy legal status of the project. Also note that this method is not unique - FSF and many other organizations require exactly the same thing.

Some contributors may have reasonable doubts about the future status of this project. Let me assure you that this project will never have more restrictive license than GPLv2. If, some time in the future, the GPL is somehow invalidated in court, the project will be re-licensed under similar (in spirit) license, if possible, or a license less restrictive than GPL (for example, the three-clause BSD license).