As I said in the past blog, in small blogs (micro-blogs) I will saw cognitive content. Random Sasha will ask me – "Why is it if we can go to the same habr?", and I will answer the fact that he is right. Only now they usually go there on such topics consciously when few people expect this kind of blogs. In fact, the one who went to SG read articles about games can be slightly immersed in the topics related to games, for example, as the main theme of the blog. Why? Because games, like everything that we have on the computer, is software. Of course, in such blogs I will not clearly paint it at a professional level, but there will be enough information for a conceptual understanding of information, because there is no point in loading the reader with complex terms. Especially if he only wants to find out a little bit, and not make his own game. Well, to be honest, it will be useful for me to go again on those topics that have long passed. I think that everything has already understood everything and we can start.
What is software?
For understanding, you need to draw a line between the program and the software:
The program is an algorithm consisting of consistently executed commands (instructions). Simply put:
This is already a program, in our case, written on Python, but with software it is not so easy.
Software (software) is a set of programs. It is according to the program that is often called, which is not quite far from the truth.
That is, if conditional Main.Py is one program, then the set of Main.Py with the same programs – already software. For convenience, there is only a executable file with a well -known extension to put and is ready.
The software is divided into:
Applied software – software that ensures the implementation of the necessary users of work. For example: Microsoft Word is a text processor (editor) that allows users to create, view and edit DOCX, DOC and others;
System software – software that performs auxiliary functions. For example: a driver for your MFP/printer/scanner;
Instrumental software – software, which is designed to create new programs and. For example: Pycharm, Visual Studio Code, Spyder Ide, Python idle, all sorts of compilers or Unreal Engine.
Now help the traveler to find the diver to what games are the games?
In addition to this kind of division, the software is also divided into free and proprietary:
Free software – open source software, the license of which gives the user the right to unlimited installation, launch, free use, study, distribution and change. Free software can be both paid and free, but mostly free, because it does not limit the buyer in free distribution of its copy. The only profit from this is that you can use the paid version stupid to support the project and the caring can buy your software;
Proprietary software – closed source software, the https://vegasmoose.co.uk/ license of which imposes any restrictions on the distribution, use and change on the owner of the copy. As a rule, they are paid and conditionally paid programs, especially games.
Licensing by software
And now we are approaching the most interesting part of this blog – licensing of software. First you need to understand why this is the most licensing.
Look, we created software and decide to distribute it without a license for free throughout the Internet, without even suspecting what consequences end users will have. The problem is that the user is nothing and using your software, which has no license, the user violates the law. The fact is that the software that you have developed can only be used by you even if voluntary drain on the Internet. All those who received your copy, using yours, violate the law and you can even sue, although this is quite strange: you yourself published it for open access, and then you can dry. Due to this, it was decided to license the software so that the user received a copy could legally use it.
Licenses are divided into:
The first type of license is a license of a public property. Just the same, this license was invented to release software from any copy of the developer. In fact, such licenses destroy the copyright law of the developer and make according to the property of a society that can do with him what wants. A vivid example will be the WTFPL license, whose abbreviation I can’t even decipher, because otherwise, otherwise SG administrators will be put there to me there. I can only mitigate to translate into Russian how to "do what you want, a public license". The Window Maker window manager for UNIX-like systems, the OpenStreetmap service and the game Liero were released under this license. As you know, because of the name, I can’t even publish the text of the license, so look for it yourself.
Allowing license (BSD-Like License, permissive license) is a type of free licenses, which practically does not tax the licensee (user) with any restrictions on the use of software. Usually they only ask to indicate the author of the original software in a file with a license, otherwise they allow to distribute, use (including commercial purposes) and modify the software. The very first of these was a BSD license for BSD family operating systems. The BSD system itself did not allow you to install and use programs without this very license. Currently, on many BSD systems, the ban has been softened and involves the use of only free licenses as: GNU GPL, MIT, Apache and others;But so far it is impossible to use the same NVIDIA drivers, only through the programs-layers in the repository of the same FreeBSD. Bright representatives of these licenses are: BSD, MIT and Apache. Below I will provide about what these licenses look like with a translation and on the original.
Dagor Engine
BSD 3-CLAUSE LICENSE
Copyright (C) 2023, Gaijin Entertainment
All Rights Reserved.
Redistribution and Use in Source and Binary Forms, With or Without Modification, Are Permited Provided that Following Conditions Are Met:
1. Redistributions of Source Code Must Retain the ABOVE Copyright Notice, This List of Conditions and the Following Disclaimer.
2. Redistributions in Binary Form Must Must Must Must Copyright Notice, This List of Conditions and the Following Disclaimer in the Documentation and/Or Other MaterialsProvided with The Distribution.
3. Neither the Name of the Copyright Holder number of Its Contributors may be uses or production products derved from This Software Without Specific SpecificPrior Written Permission.
This Software is ProvideDed by the Copyright Holders and Contributors "AS" and Any Express Or Impled Warranties, Including, But Not Limited to, The ImpliedWarranties of Merchantability and Fitness for a Particular Purpose Are Disclaimed. In no event shall the copyright holder or contributors be liable for ain direct, indirect, Incidental, Special, Exemplary, Or Consequential Damages (Including, ButNot Limited to, Procurement of Substitute Goods Or Services;Loss of Use, Data, Or Business Interruption)CONTRACT, StRICT LIABILITY, OR TORT (Including Negligence or Otherwise) Arising In Any Out of the Use of this Software, Even IF Advisned of the Possibility ofSuch Damage.
=============================================================================================================
FIRST-PARTY Software Distributed with Dagor Engine: Licensing and Copyright Information
=============================================================================================================
The Dagor Engine Software Includes Other Code Developed by Gaijin Entertainment Aside from the Main Software. Each of these First-Party Components Has Its Own License.TXT or Similar Document Specifying Its Licensing Terms That May Significantly Differ From this License. These Files Are Located in the Respective Directories of Each First-Party Component as Follows:
The Dagor Engine Software Incorporates Code Developed by Third-Party Contributors. Each of these Third-Party Components Comes with its Own License.Txt or similar Document Specify Its Copyright Attribution and Licensing Terms that May Significantly Differ From this License.
Please Note that Gaijin Entertainment Assums No Responsibolyity, Liabiley, Obligations Whatsoever for the Third-Party Components and Their Use by. You Shoup Adhere to and Further Comply with the Licensing Terms OutLined by Third-Party Components. You agree to indemnify, defend, and hold harmless Gaijin Entertainment from and against any and all claims, damages, obligations, losses, liabilities, costs, debts,And Expenses (Including But Limited to Attorney’s Fees) Arising from Your Failure to Comply with Them.
We Recomment Consulting the Respective License.Txt or Equivalent Files for Your Guidance. You can find theom in the Respective Directories of Each Third-Party Component as Follows:
BSD license, 3 points
Copyright (C) 2023, Gaijin Entertainment.
All rights are protected.
Distribution and use in the original and binary form, with or without modifications, is allowed subject to the following conditions:
1. With the repeated distribution of the source code, the above -mentioned copyright notification, this list of conditions and the next rejection of liability should be maintained.
2. With repeated distribution in binary form, the aforementioned copyright notification, this list of conditions and the following rejection of responsibility in the documentation and/or other materials supplied together with the distribution.
3. Neither the name of the copyright owner, nor the names of its participants can be used to support or promote products created on the basis of this software without a special preliminary written resolution.
This software is provided to the owners of copyright and the participants “as is”, and any obvious or implied guarantees, including, but not limited, implied with guarantees of commodity fitness and suitability for a specific purpose, refuse. Under any circumstances, the owner of the copyright or participants are responsible for any direct, indirect, random, special, approximate or indirect losses (including, but not limited, the purchase of replacing goods or services; loss of use, data or profit; or interruption of business activity), any caused, and on any theory of responsibility, as a contract, strictly or offenses (including non-negligence or non-negligence or otherImages) arising in any way to use this software, even if they are notified of the possibility of such damage.
=============================================================================================================
Third -party software distributed using Dagor Engine: Information about licensing and copyright
=============================================================================================================
Dagor Engine software includes another code developed by Gaijin Entertainment, in addition to the main software. Each of these third -party components has its own License file.txt or a similar document that determines licensing conditions that may differ significantly from this license. These files are located in the corresponding catalogs of each main component as follows:
=============================================================================================================
Third -party software distributed from Dagor Engine: Information about licensing and copyright
=============================================================================================================
Dagor Engine software includes a code developed by third -party participants. Each of these third -party components is supplied with your own License file.txt or a similar document, which indicates copyright and licensing conditions, which may differ significantly from this license.
Please note that Gaijin Entertainment does not bear any responsibility or obligations regarding third -party components and their use by you. You must comply with and further comply with the terms of licensing set forth by these third -party components. You agree to compensate for losses, protect and protect the Gaijin Entertainment from any and all claims, losses, obligations, losses, liability, costs, debts and expenses (including, among other things, the fees of lawyers) arising from your non -compliance with their non -compliance.
We recommend that you seek the help of the corresponding License file.txt or equivalent files. You can find them in the appropriate catalogs of each third -party component as follows:
Copyright (C) 2014-Pressent Godot Engine Contributors (See Authors.MD).
Copyright (C) 2007-2014 Juan Linietsky, Ariel Manzur.
Permission is Hereby Granted, Free of Charge, To Any Person Obtaining a Copy
Of this Software and Associated Documentation Files (The "Software"), to Deal
In the Software Without Restriction, Including Without Limitation The Rights to Use, Copy, Modify, Merge, Publish, Distribute, Sublicense, And/Or Sell CopinesOf the Software, and to permit persons to whom the software is furnined to do so, subject to the following concights:
The ABOVE Copyright Notice and this Permission Notice Shall BE Included in All
Copies or Substantial Ports of the Software.
The Software Is Provided "As is", Without Warranty of Any Kind, Express or ImpLied, Including But Notes to the Warranties of Merchantability, Fitness for AParticular Purpose and Noninfringement. In no event shall the authors or copyright Holders be Liable for Any Claim, Damages or Other Liability, Hether in An Action of Contract, Tort or Otherwise, Arising From, OutOf or concedion with the software or the use or oter dealings in the Software.
Copyright (C) 2014-Pressent Godot Engine Contributors (See Authors.MD).
Copyright (C) 2007-2014 Juan Linietsky, Ariel Manzur.
Permission is Hereby Granted, Free of Charge, to Any Person Obtaining a Copy of this Software and Assocument Files (The "Software"), to Deal in theSoftware Without Restrication, Including Without Limitation the Rights to Use, Copy, Modify, Merge, Public, Distribute, Sublicense, and/Or Sell Copies of theSoftware, and to permit persons to Whohom The Software Is Furnished to Do So, Subject to the Following Conditions:
The ABOVE Copyright Notice and this Permission Notice Shall BE Included in All Copies Or Substantial Ports of the Software.
The Software Is Provided "As is", Without Warranty of Any Kind, Express or ImpLied, Including But Notes to the Warranties of Merchantability, Fitness for AParticular Purpose and Noninfringement. In no event shall the authors or copyright Holders be liable for Any Claim, Damages or Other Liability, Hether in An ActRACT, Tort Or Otherwise, Arising From, OutOf or concedion with the software or the use or oter dealings in the Software.
Copyright (c) authors of Godot Engine, 2014 – present (see. Authors.MD).
Copyright (c) 2007-2014 Juan Linia, Ariel Manzur.
This permit is provided for free to any person who received a copy of this software and related documentation files (“software”) to use software without restrictions, including, among other things, the right to use, copy, change, association. Publish, distribute, sublicense and/or sell copies of software, as well as allow the persons to be provided with software, to do this subject to the following conditions:
The aforementioned copyright notification and this notification of permission should be included in all copies or essential parts of the software.
The software is provided “as it is”, without any guarantees, obvious or implied, including, but not limited, guarantees of commodity value, suitability for a certain purpose and non-war of rights. Under no circumstances, the authors or owners of copyright are not responsible for any claims, losses or other liability, whether in actions under the contract, offense or in another way arising from, from or in connection with the software or use or other transactions, software, software.
Original (I have when copying with github, problems with retreats and paragraphs that I have tired of correcting, so I had to go through an insert of code). You have enough examples, so there will be a short version of the Apache license from the official site
License with copyright left law (license coplets, licenses of the author’s leve) is a type of free licenses, the difference. Copilet – an obligation prescribed in a license, which provides that in case of modification of free software (it does not matter who), which is under the same license, it will remain free and open. That is, if I take and upgrade the game with coplets with a license and it was free, then I can’t sell it or later close it from prying eyes.
A striking example of such licenses will be not one, but a conditionally family of GNU General Public License: GPLV3, LGPL, AGPL licenses. In general, GPL is the first copy of the license, which is known for history. According to the first, it was only one license, but as necessary, it was necessary to add LGPL and AGPL.
LGPL (Lesser General Public License) is a free copulant license, which provides for the possibility of lining (communication, association) with proprietary (closed) software. This license provides for limited freedom for users in those components of proprietary software, which were licensed by LGPL. LGPL is usually used in the framework of libraries of programming languages. The very appearance of LGPL was due to the fact that before this libraries with the GPL license obliged developers to make free software. With the advent of LGPL in the libraries that are licensed by it, the copypool spreads only within the framework of this very library.
AGPL (Affero General Public License) is a free copulant license, which was created to licensing sites and web applications with open source codes.
Conditional software license – type of proprietary software licenses, which involves free use with certain conditions. This kind of license can be either copyright (the developer himself formed a license), or template by Freemium, Donationware, AdWare and others. Typically, such licenses are used in various free games in the type of War Thunder (Gaijin license), demo versions of games, subscription programs and even really free programs in which commercial use is prohibited or only personal use is allowed.
Well, the last type of license today is its own. We previously mentioned them in the context of the licenses of conditionally paying software, but here we will consider more comprehensively.
Own license (EULA or a familiar "user agreement") is the type of proprietary software licenses in which the developer himself draws up a licensed agreement with the licensee (user). This type of licenses is the most common in the world, because it is more profitable for large companies to create the conditions for their use by end users themselves.
Usually, EULA changes unilaterally from the developer, but few pay attention to this. And in general, gamers do not pay attention to what they sign. For example, from this kind of change, this is a quick addition of a new item in Activision about monitoring, which generally provides that the company’s games can monitor all the processes you have started allegedly to prevent unauthorized access to the work of their game (that is, to combat cheats).
Well, or from a rather interesting one, is that Gaijin license prohibits playing at the same work. Honestly, I don’t even understand why. Apparently playing War Thunder, we can somehow use it for commercial purposes.
I think we have already learned a lot today, but it’s time for us to say goodbye. If you want to read something else from my work, then below you can find links to other blogs. Good luck to everyone and see you in the next blogs!
UPD: To be honest, I don’t understand why, after each editing, even the name of the blog, the blog itself flies into the premotage as if it has suspicious elements. By virtue of this, I ask you to support the blog with my royal plus for my patience with the premotiation, because even after a bunch of checks before publication, I still make editing or improvements somewhere so that it is more pleasant for you to read.