Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Repo Has No License

未关闭
#97 12 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
html

调研方向

检查所引用的 home.yml、assets/globals/home、_layouts/home.html 和 cn 翻译树,然后将它们与链接的历史修订进行比较。在更改受影响的内容之前,解决所提出的 MIT 与 CC 许可以及贡献者许可权限问题。完成的标准是:保留的内容已获得许可,许可决定已记录,并且已添加仓库许可证。

由索引模型根据 Issue 内容生成。

描述

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.

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

主要语言
HTML
星标
1.5k
派生
360
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

termux/termux.github.io 的其他 Issue

查看 termux/termux.github.io 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。