-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion about adding Anti-996 to Github official 关于让Github官方认可Anti-996 license的讨论 #11
Comments
It mentioned that only a small number are highlighted on the home page and
Right now there is more than 1600 repos using 996 license by github search . So Item No.3 has Fitted, but the consensus in 996 licenses are not. As for Item No.4, there is 996.ICU, 955.WLB and Anti-996-License and a lot of repos with stars more than 3k. I am not sure about the word "notable ". I think Item No.4 is fitted. |
I don't think Item No.4 is necessarily fitted. This may be the first time GitHub - even the entire open source community - has ever seen a movement producing a license based on several GitHub Repos. I personally think GitHub is establishing Item No.4 to illustrate the influence the license should be having out in the actual open source community rather than the movement community itself. I honestly don't think using our own repos for Item No.4 can be actually seen as fitted. |
@zangyongyi How about this: AwesomeList. After all, it depends on how GitHub defining the "notable project". |
@ff4415 @zangyongyi whats the progress so far? sorry didnt follow up in the past 2days. |
I think most of these requirements is already satisfied? |
个人感觉 列出的4条,后面两条已经或者几乎已经满足。 SPDX 需要有人提交申请走流程。 第二条需要 license 和开源社区兼容。 |
第二条要等意见。类似于GNU完全可能重新讨论。但是OSI我觉得不太会立刻支持 |
@ff4415 有没有可能有一种别的方法(除了等github官方),比如一个浏览器插件?脑洞 |
感谢反对996的每个人,割韭菜喽割韭菜 |
https://www.fsf.org/blogs/licensing/a-roundup-of-recent-updates-to-our-licensing-materials-november-2018-to-june-2019 See: https://radicalxchange.org/blog/posts/2019-05-31-tz00lw/ |
是 |
No description provided.
The text was updated successfully, but these errors were encountered: