Repo Has No License

Currently and since start of this repo, the license was not supplied so all contributions are technically under copyright of original authors and not licensed to be used by others.

https://github.com/termux/termux.github.io/commits/master?after=cb0333aedd959214223262ea54c128cbbde2f266+244&branch=master&qualified_name=refs%2Fheads%2Fmaster

Basically, we need to add a license. The site infrastructure in my opinion should be MIT licensed so that the multi-translation, multi-versioned, and web/android supported design being built can be used by other projects easily. The docs are pulled from other repos as well so community contributed docs should be permissively licensed (MIT/CC) and GPLv* shouldn't be enforced on them.

I have diffed master against 89b58fc8 and due to my rewrites of the site since I took over, the only parts that remain same is the home page words for english translation, images and the code for image rotation. So before a license can be added, the images need to be replaced and words changed if required, although only very minimal.

• https://github.com/termux/termux.github.io/blob/cb0333aedd959214223262ea54c128cbbde2f266/_data/t/en/views/home.yml
• https://github.com/termux/termux.github.io/tree/cb0333aedd959214223262ea54c128cbbde2f266/assets/globals/home
• https://github.com/termux/termux.github.io/blob/cb0333aedd959214223262ea54c128cbbde2f266/_layouts/home.html#L6

There was also chinese translations done by @2096779623, @licy183 and @DreamOneX and they all need to provide written proof below that their contributions can be released under the new license after its chosen.

https://github.com/termux/termux.github.io/tree/cb0333aedd959214223262ea54c128cbbde2f266/cn

There is an additional issue, the contributions to https://wiki.termux.com/wiki/Main_Page are under Creative Commons Attribution license, which is not compatible with MIT and only GPLv3, so moving the wiki content to the site would be problematic, unless a complete rewrite is done or permission is taken from authors to relicense. We can also go with licensing the site infrastructure as MIT and the docs/posts/translations as CC, which would then solve the wiki problem.

Edit: I would prefer docs to be MIT to be consistent with lot of the code, and adding yet another license on top of MIT and GPLv3 complicates things for contributors and forkers. We can always ask wiki page authors for permission to relicense to MIT. One can always relicense MIT files under any more restrictive license, but with CC, only 2 options currently available. Basically, I am personally against CC for docs.

https://creativecommons.org/licenses/by/4.0/

https://opensource.stackexchange.com/questions/7435/mit-licensed-project-with-cc-by-sa-dependency

https://creativecommons.org/share-your-work/licensing-considerations/compatible-licenses

This should be done before the next termux app release which provides new docs.

@Grimler91 @sylirre

Review the referenced home.yml, assets/globals/home, _layouts/home.html, and the cn translation tree, then compare them with the linked historical revision. Resolve the proposed MIT-versus-CC licensing and contributor-permission questions before changing the affected content. Done means the retained content has permission, the licensing decision is documented, and the repository license is added.