-
Notifications
You must be signed in to change notification settings - Fork 0
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
About Conflicts With Mirai Team #2
Comments
Preface本文记录本人于Mirai开发者(Mamoe)的冲突的详细过程 |
Scene 1由于在2020年8月底Mirai方修改了开源协议,且协议内容自相矛盾,为了确定使用Mirai时的注意事项,主动参与相关Issue mamoe/mirai#510 的讨论 |
Scene 2在同一时间,Mirai提交了名为“add sound clear”的Commit(mamoe/mirai@f6f472c),在README.md的声称“Mirai 在各个平台均没有任何所谓官方交流群或论坛”,由于我看到README.md中仍然带有Gitter Badge,因此以爱好者身份进行了review并提交了评论 |
Scene 3Mirai在名为“Original AGPLv3”的Commit中删除了Gitter Badge(mamoe/mirai@adf0299),由于该Commit的提交信息完全没有描述删除Gitter Badge的行为,因此我在后续与Mamoe的联络中曾将此次修改描述为“偷偷的解决”(Mamoe的人似乎在早期将此描述误解为指责他们偷偷修改License,详见 Scene 4) |
Scene 4在被Mirai官方封禁后,本人使用Email联系了Mamoe Support尝试进行申诉: Email 1(我)
Email 2(Mamoe)
Email 3(我)
邮件原文:9.zip |
Scene 5由于@PeratX 的言语几乎动摇了OSS的根基,且@mzdluo123 直接对我进行了block,我尝试添加他的QQ,验证信息中表达了希望解除block的心愿。 |
Scene 6在后期,Mirai又在README.md中添加了Gitter Badge,并声明除Gitter和Github外无其他官方讨论组(说明本人在Commit下的疑问是正确的),此时本人尝试通过Gitter与Mirai联系解除block,位置ID:5f7584cba7389b19f0ede14b |
离线Markdown文件备用:About Conflicts With Mirai Team.zip |
No description provided.
The text was updated successfully, but these errors were encountered: