kreyren/Zernit
1
0
Fork 0
Code Issues 129 Pull Requests Releases Activity

fjfdgjdf

Browse Source
This commit is contained in:
Kreyren 2020-02-17 14:31:35 +00:00
parent 75a001ea68
commit 732ea66f3d
1 changed files with 41 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
LICENSE/EN-LICENSE.md
View File

@ -19,7 +19,7 @@ Redistribution of this license is not allowed unless explicitly stated in the li
<center><h4>Preamble</h4></center>
This license is made to protect the intellectual property and direct workflow of project codenamed as **RXT0112** also known as **Zernit** publicly represented on hyperlink https://github.com/RXT0112/Zernit and understood as original repository where this license is developed based on [GPL-3 license](https://www.gnu.org/licenses/gpl-3.0.en.html) and [Free Software Foundation](https://www.fsf.org) philosophy adapted for commercial use and to avoid segmentation while providing sustainable business plan with the intention to provide open-source software for everyone.
This license is made to protect the intellectual property and direct workflow of project codenamed as **RXT0112** also known as **Zernit** publicly represented on hyperlink https://github.com/RXT0112/Zernit and understood as original repository where this license is developed based on [GPL-3 license](https://www.gnu.org/licenses/gpl-3.0.en.html) and [Free Software Foundation](https://www.fsf.org) philosophy adapted for commercial use with the intention to avoid segmentation while providing sustainable business plan to provide open-source software for everyone.
License is designed to be community maintained where only the authorized personel further identified in this file are permitted to make changes in the original repository in which this license has been created.
These authorized personel can be also clarified in file located in `.github/CODEOWNERS` with syntax explanation on hyperlink https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners to appropriate GitHub Team or personal to allow making changes in this file which has to be archived using `git` which is version-control system for tracking changes in source code further explained by it's maintainers on hyperlink https://git-scm.com/.
@ -29,6 +29,8 @@ This file is written in markdown syntax further explained on hyperlink https://e
## 0. TERMINOLOGY
This section is dedicated to provide explanation of used terms in this file.
You are encouraged to contribute in case required explanation of used terms is missing or is not sufficient.
### Comments
Comments are a feature in markdown syntax that do not render the appropriate section specified by this syntax on the final version and is not meant to be a part of final version due it's usage for development of this license.
@ -45,7 +47,7 @@ FIXME comments are lines in this documment prefixed with `FIXME:` which are also
Example of FIXME comment:
FIXME: Hello, i'm example
FIXME: Hello, i'm example of FIXME comment
### Source code
Source code is a collection of text recognized by compiler that are used to perform specified action in the hardware itself.
@ -61,9 +63,6 @@ Unless it is not obvious paths are representing physicall files or directories i
path `src/bin/main.rs` points to file located in repository use
### License Managers (or 'LM' for short)
**L**icense **M**anagers clarified in path `.github/CODEOWNERS` on original repository in this repository are authorised personnel with permission to perform changes in LICENSE files.
### Original Creator (or 'OC' for short)
Original Creator of this repository is `Jacob Hrbek <kreyren@rixotstudio.cz>`.
@ -75,20 +74,25 @@ OC reserves absolute right for whole repository to decide hierarchy of parties a
Repository Managers are defined as service with the ability to provide our project for the general public in on-line form.
### Merge Request
Also wrongly named as 'Pull Requst' by many RMs is method to submit new changes in the target repository.
Also wrongly named as 'Pull Requst' by many repository managers is method to submit new changes in the target repository.
#### Draft Merge Requests
Referencing https://github.blog/2019-02-14-introducing-draft-pull-requests/ for upstream (github) explanation.
Referencing https://github.blog/2019-02-14-introducing-draft-pull-requests/ for upstream (GitHub, Inc.) explanation.
In short this is merge request which is being worked on before it can be submitted for review and considered for merge.
In short this is merge request which is being worked on before it can be submitted for review and considered for merge in target repository.
### Forks
Forks are repository manager's features that allows anyone to make a copy of a repository in their specified profile.
## 1. CONDITIONS
### Agreenment
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the provided content on original repository (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
### Conflicts with local laws
This license explicitly does not allow any use of RXT0112's intellectual property in a scenario where license implementation conflicts with local laws in the area of use of said intellectual property.
For the license to grant expected permission you are required to inform the project about said conflicts with proper references and/or submit a merge request with required improvements to allow these expected permissions.
### Your agreenment
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify, use or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by using, modifying or distributing the intellectual property of project RXT0112 (or any work based on the Program), you indicate your acceptance of this License to do so, and in all of its terms and conditions.
### Contributions
Everyone is allowed to fork this repository as long as the source code stays public with the intention to provide a contribution to the original repository.
@ -108,7 +112,7 @@ Created by Jon Doe <jon@doe.wow> using LICENSE (hyperlink://on.theLicense.wow) i
- `LICENSE` or `LICENSE.md` file created in the root of directory which will be applied for the whole directory.
All affiliated parties that changed content provided in original repository are required to place following signature in their commit messages to prove that they agree with terms provided in said license and the terms in following versions.
All affiliated parties that changed content provided in original repository are required to place following signature in their commit messages to prove that they agree with terms provided in said license and the terms in following versions which they have the right to influence.
```
Signed-off-by: Jon Doe <jondoe@example.foo>
@ -121,8 +125,32 @@ Example of syntax used for versioning:
**18061016022020** meaning **16th February of the year 2020 at 18 hours, 6 minutes and 10 seconds**
## 2. Warranty
## 2. Your permission
These permissions are granted as part of our ongoing effort to comply with Free Software Foundation's philosophy, it's as of 17/02/20 is not perfect based on majority of FSF members discussed in https://forum.members.fsf.org/t/help-me-with-gpl-3-inspired-license-designed-for-commercial-use-and-to-avoid-segmentation/1953/59 and we encourage contribution and challenges if you have a better solution since it's in our best interest to provide best possible environment for further development and end-user satisfaction.
This program is provided without any warranty unless required by law in which case the party which requires said implementation of law in this license is required to inform the project for said laws to be adapted in this license so that the the program can be used legally in their area.
### Use of intellectual property for personal use
Assuming that conditions in this license are not breached then you are allowed to use intellectual property of project RXT0112 for personal use unless stated otherwise by other license which use is specified in contributing condition.
### Permission to modify the intellectual property
You are allowed to perform any changes to the intellectual property that does not include features that are suitable for original repository.
You have the right to modify and/or maintain specific section of a project in original repository with official support and guidance from the project for free as long as your contribution passes code quality checks (excluding false trigger caused by a bug) and review from other contributors.
You have the right to use your contribution outside of original repository if maintainers of original repository does not allow for the feature to be implemented.
### Distribution of malware
We do not grant you a permission to distribute our intellectual property with a malicious code that is directly and/or indirectly made to harm the end-user which includes handling of end-user's data without explicit permission by the end-user.
### Usage by whitehat hackers
You have the right to use intellectual property with the intention to fix security issues in our project and other systems as long as your work does not directly harm our project.
White hat hackers are also welcomed by the project and their work is highly appreciated.
### Usage in weapons
We do not grant you a permission to use our intellectual property as a part of a mechanism that is designed to cause a harm to a living organism.
## 3. Warranty
This program is provided without any warranty unless required by law in which case the party which requires said implementation of law in this license is required to inform the project for said laws to be implemented in this license so that the the program can be used legally in their area as stated in conditions above.
Warranty can also be specified based on invidual contract or agreenment with party that requires it.