- 瑞典旅游-伤心之旅 [2018/09]
- 从张成泽被处决的事情看，有三个方面的意义 [2013/12]
- 鞋子落下来了；MD安德森谢教授不光是裸照 [2018/10]
- --从温家宝家族贪污传闻想起赵紫阳儿子倒彩电 ZT [2012/11]
- 加入混战 【少儿不宜】 [2011/02]
- 终于知道了一点艾未未 [2011/04]
- 男性更年期的臭事 [2013/05]
- 牢骚 多了 [2014/03]
- 体味和口臭 [2014/09]
- 明大LINUX事件的反思（1）小P点燃导火线 [2021/04]
- 庄则栋的故事中俺看到的日本 [2013/02]
- 铊毒案 后面的评论 ZT [2011/02]
- 雾霾的原因： 风力发电 [2016/12]
- 也说一下ISIS 2015-11-15 [2015/11]
- 瞎说几句薛峰的事情 [2010/07]
- 无稽之谈之芦花鸡 [2011/11]
- 韩寒 方舟子 和解滨 [2012/01]
- 少吃饭、多买名牌 [2011/12]
- 『自己做事（Do it yourself)可真难啊』学习体会--running title 我的一个星期六 [2010/12]
- 和谐的线； 顺便和稀泥 [2012/01]
- 拿到桌子上 [2012/05]
- 家有闺女初长成 [2011/10]
- 不是一般地高 [2011/03]
- 好男人的标准 [2012/06]
- 为夫为妇当如63 [2011/06]
- 俺父亲节这一天 [2012/06]
- 鸡蛋碰石头 [2010/10]
- 能说会道 多么美妙 [2011/09]
This report summarizes the events that led to this point, reviews the "Hypocrite Commits" paper that had been submitted for publication, and reviews all known prior kernel commits from UMN paper authors that had been accepted into our source repository. It concludes with a few suggestions about how the community, with UMN included, can move forward.本报告总结了到此时的所有时间， 审查了明大“假装好意提交”的文章，和其作者以前提交的补丁。本报告提出几个建议以便社区包括明大可以向前看
Moving forward
The Linux kernel was started by a university student, and there have been strong ties between the kernel and academic communities ever since. This collaboration is beneficial both to Linux, which gains from the work and ideas of researchers, and to the research community, which is able to work with a heavily used kernel and see its ideas deployed in practice. This collaboration is worth preserving -- and, indeed deepening. The incident described in this paper is seen by some developers in both camps as a threat to that collaboration, but it need not turn out that way.
We have two specific recommendations designed to ensure that the kernel project and UMN can continue to work together successfully in the future:
- UMN must improve the quality of the changes that are proposed for inclusion into the kernel, and
- The TAB, working with researchers, will create a document explaining best practices for all research groups to follow when working with the kernel (and open-source projects in general).
The combination of these two changes, we hope, will help the kernel and research communities to work together fruitfully and prevent incidents like this from occurring again.
Development process changes
In the past, the kernel community has often had to deal with a pattern of low-quality patches originating from a single company or group. These patches consume scarce maintainer time and, over time, lead to tense relations between the two groups. In such cases, the kernel community has worked with the companies involved to set up internal procedures to make the patch creation and submission process work better. When set up properly, such a process can reduce the mentoring load on kernel maintainers and enable contributors to be more successful in their work.
A common practice in many companies is to designate a set of experienced internal developers to review and provide feedback on proposed kernel changes before those changes are submitted publicly. This review catches obvious mistakes and relieves the community of the need to repeatedly remind developers of elementary practices like adherence to coding standards and thorough testing of patches. It results in a higher-quality patch stream that will encounter fewer problems in the kernel community.
We believe that UMN could benefit from a review process of this type, and recommend that UMN find at least one experienced developer to fill this role. Having such a reviewer in place could have prevented the submission of many of the flawed patches described here. Working with an experienced developer can also help UMN researchers toward better interactions with the kernel community and would, hopefully, prevent concepts like the "Hypocrite Commits" project from getting beyond the idea stage.
Until such a review process is put into place, it will be difficult to re-establish the trust between UMN and the kernel community, and patches from UMN will continue to find a chilly reception. If UMN needs help to find such a developer or to set up an internal review process, the TAB will be glad to assist. This is a role the TAB has played with many groups in the past.