大多数人认为开源项目具有以下共同的特性:•源代码访问当然，可能还有其他一些通常被认为是特性的项目，但是，我想关注第二点;提交代码更改的过程。如果一个开源项目拥有上面所有的特性，除了不接受代码更改外，它就不再是一个开源项目了吗?举个例子，几年前，当Zimbra首次被雅虎收购时，我参加了一个会议，Zimbra的负责人讨论了为什么99.5%的代码是由Zimbra的员工编写和维护的，而不是更广泛的社区。事实上，Zimbra对让外部各方提交代码不感兴趣，因为他们的开发过程被严格管理并通过内部过程运行。任何想要查看或下载它的人都可以公开获得源代码。因此，我认为它们是一个开源项目。另一个例子是SugarCRM。他们目前提供解决方案的“社区”版和用户购买的“企业”版。进一步的审查表明，社区版是公司版的一个子集; however all the code is open sourced and written directly by SugarCRM employees. The community input for SugarCRM is focused on technology add-ons in their ecosystem solution set and not within the core SugarCRM technology. Thus, I also consider them an open source project. In both examples, the company maintains control of the core project and is not in the business of asking for development assistance. The software is open sourced however the project is not setup to accept code submissions, as you would see with the Linux kernel, for example. I believe these companies are running another type of open source project and should be categorized as such. However, some people argue that without accepting code from independent sources, these projects are not open source. What are your thoughts?
•处理提交代码更改
•处理提交bug
•文档(质量级别不同)
•项目商标的所有权
•公开发布时间表