Provide a convenient way to get a written permission to edit the source code

[WeetHet]

According to the license

Modification <...> is strictly prohibited without prior written permission from the copyright holder.

But there's no convenient way to acquire such a permission. I propose a creation of a list of people allowed to edit the repo as a markdown file inside the repository, something like EDITORS.md. #228 could also address this issue, but in the current state, this is the best solution I can come up with. By filing this issue I also request the permission to modify the source code from the authors

[AShepelevv]

Thank you @sweetheart for your message! You are right, we have not provided any instructions on this matter. Therefore, you can write an email to [email protected], where you can describe the purpose of the allowance and provide your contact information. The response email will be an official decision from the authors. If the decision is positive, you will be able to use the source code according to the terms of the allowance.

---

Furthermore, there is another scenario where you do not need an allowance. You can create a branch in this repository, commit your changes, and submit a pull request to merge your changes into the master branch. These changes won't be considered as your personal modifications. And the license does not restrict that.

---

In addition, I will add these instructions to the README file.

Thank you for the notice!

[WeetHet]

Furthermore, there is another scenario where you do not need an allowance. You can create a branch in this repository, commit your changes, and submit a pull request to merge your changes into the master branch. These changes won't be considered as your personal modifications. And the license does not restrict that.

That is generally not true, as creating a pull request requires forking and modifying the forked copy which is generally accepted to be counted as "modification". Therefore, as I can't ensure that I'm not breaking the license, I'll abstain from contributing by forking and creating a PR until the license is corrected to allow such kind of behaviour without a written permission or getting such a permission

[AShepelevv]

creating a pull request requires forking and modifying the forked copy

You do not really need to fork repository to create a Pull Request. It is enough to create a branch, commit to the brunch, push it and create a Pull Request inside this original repository.

[averyanalex]

creating a pull request requires forking and modifying the forked copy

You do not really need to fork repository to create a Pull Request. It is enough to create a branch, commit to the brunch, push it and create a Pull Request inside this original repository.

Creation of branch is a creation of derivative version, and publishing it to the github is a distribution. Also, only developers of the original repo can push to it, other people must create fork to submit PR.

[WeetHet]

creating a pull request requires forking and modifying the forked copy

You do not really need to fork repository to create a Pull Request. It is enough to create a branch, commit to the brunch, push it and create a Pull Request inside this original repository.

I don't have write access to the repo, so I can't create a branch in the original repo

[AShepelevv]

I am really sorry about my mistake. I did not know that non-collaborators must have the push permission to create a branch in a public repository. Therefore, the license has been changed according to #228. Thank you all for your help!

If you want to contribute frequently to the repo, we can discuss giving you a collaborator role.