mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
[翻译完成][talk]How the Apache Software Foundation selects open source projects
This commit is contained in:
Hans zhao
GitHub
parent
88ea029b1c
commit
b14c32b71f
@ -1,65 +0,0 @@
|
||||
[#]: subject: (How the Apache Software Foundation selects open source projects)
|
||||
[#]: via: (https://opensource.com/article/21/6/apache-software-foundation)
|
||||
[#]: author: (Justin Mclean https://opensource.com/users/justin-mclean)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (hanszhao80)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
How the Apache Software Foundation selects open source projects
|
||||
======
|
||||
The Apache Software Foundation (ASF) is built around a unique set of
|
||||
processes and values to ensure openness.
|
||||
![Wide open sky and trees][1]
|
||||
|
||||
As a longtime volunteer and mentor (and current board member) at the [Apache Software Foundation][2] (ASF) and vice president of the Apache Incubator, I'm proud to offer my insights into the unique processes and values with which the ASF operates.
|
||||
|
||||
Centered upon the permissive and pragmatic open source [Apache License][3], the ASF conducts itself differently from many other foundations simply because it is a charitable organization constructed for the public good. For example, the ASF board is elected by members. No one can buy a seat on the board, and the ASF's affiliations are with individuals, not companies. Generally, the corporate affiliation of any individual involved with ASF goes unstated, and it doesn't matter. As an outcome, the ASF has fostered a vendor-neutral environment where companies can comfortably collaborate on building valuable projects.
|
||||
|
||||
Let's take a look at how the ASF selects its projects, the state of open source licensing today, and what you can expect from the ASF heading into the future.
|
||||
|
||||
### The Apache Incubator process and 'The Apache Way'
|
||||
|
||||
Potential Apache projects begin in the [Apache Incubator][4], where they receive assistance and mentoring toward their hopeful graduation as top-level Apache projects. Anyone is welcome to put together a project proposal for the Incubator (they simply need to find someone inside the ASF who's willing to help champion it). When vetting a potential project, the ASF prefers to see a diversity of people and entities involved—and certainly not just a singular corporate body. We've found this greater diversity results in projects that are more widely used and longer lasting.
|
||||
|
||||
The central purpose of the Incubator is to help projects learn and operate in alignment with what we call [The Apache Way][5]. It is a set of values that inform best practices for community-led development. The most important aspects of The Apache Way include strict vendor-neutral independence and prioritization of a strong community, even over the strength of a project's code. Open and transparent communication is crucial as well: The ASF requires that all project communication is publicly accessible and permanently archived to enable asynchronous collaboration. In addition, the open source Apache License is attached to all accepted projects, ensuring that all source code is publicly available as well.
|
||||
|
||||
At the Incubator, we initially look at whether a project is a good fit in terms of how it aligns with these Apache values. It isn't necessary to have 100% alignment, but the project needs to be willing to adapt. There will also be a discussion around ensuring that the project is fully compatible with Apache from a licensing perspective—in some scenarios, dependencies will be removed or replaced as needed. The Apache Way prepares projects to build communities that are self-sustaining. That said, it can be difficult for some projects to build a community, and some don't make it through the incubator.
|
||||
|
||||
Another key element of The Apache Way—one essential to thriving communities—is making decisions based on consensus. In our experience, open discussions and avoiding a single individual project leader are mission-critical to that process. We have had a couple of incubating projects that included a strong personality trying to retain control, and well, those projects didn't succeed for that reason.
|
||||
|
||||
### Open source and the Apache License
|
||||
|
||||
Open source projects come in many varieties. At the same time, using an open source license doesn't automatically make a project open source. It's a project's community that unlocks open source benefits and whose contributions precipitate greater openness and transparency.
|
||||
|
||||
Recently, some companies have made high-profile moves away from the Apache License to less-permissive licensing. If your company changes from an open source to a non-open source license, I have to question why you had that open source license in the first place. It probably meant that the business model didn't fit open source. I believe that by changing away from open source licenses, companies are doing a huge disservice to their communities and their users.
|
||||
|
||||
As I said, the ASF is a non-profit, charitable organization that creates software for the public good. That's the purpose of the permissive Apache License. Making money off that software is fine, but that's not what the Apache License is about. As a rule, ASF disallows any field-of-use restrictions. _Anyone_ can use Apache projects for any reason. The idea behind true open source is that some people who use a project will give back to it, but contributions absolutely cannot be required. The companies that seem so hung up on that point need to understand that isn't how open source works, and that isn't how it should work.
|
||||
|
||||
### The future of open source and the ASF
|
||||
|
||||
Open source has certainly seen outsized adoption in the last five to 10 years and particular acceleration among enterprises. I think it's safe to say that there's hardly any software on the planet that doesn't include or rely upon open source projects in some way. That adoption is only going to grow.
|
||||
|
||||
Unlike some foundations, the ASF is fairly hands-off in terms of project recruitment. Expect the ASF to continue as it has, stating the values of The Apache Way and working with those projects that see value in the ASF's approach. With ASF projects leading at the forefront of major industry shifts—initially with web servers and more recently with big data through projects like Apache Hadoop and Spark, Cassandra, and Kafka—the hands-off stance has shown to be successful and sustainable.
|
||||
|
||||
When it comes to what's next, the ASF has several large and buzzed-about artificial intelligence and machine learning projects. In addition, several Internet of Things (IoT) projects have also been passing through the Apache Incubator, some of which will likely become quite influential. Looking forward, expect the ASF to continue as it has, introducing some hugely successful open source projects used by major industry players, with other smaller projects providing vital—if more niche—appeal.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/6/apache-software-foundation
|
||||
|
||||
作者：[Justin Mclean][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[hanszhao80](https://github.com/hanszhao80)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/justin-mclean
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/nature_open_sky_tree.png?itok=2J79Futp (Wide open sky and trees)
|
||||
[2]: https://www.apache.org/
|
||||
[3]: https://www.apache.org/licenses/LICENSE-2.0
|
||||
[4]: https://incubator.apache.org/
|
||||
[5]: https://apache.org/theapacheway/
|
||||
@ -0,0 +1,63 @@
|
||||
[#]: subject: (How the Apache Software Foundation selects open source projects)
|
||||
[#]: via: (https://opensource.com/article/21/6/apache-software-foundation)
|
||||
[#]: author: (Justin Mclean https://opensource.com/users/justin-mclean)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (hanszhao80)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
Apache 软件基金会如何选择开源项目
|
||||
======
|
||||
<ruby>Apache 软件基金会<rt>ASF</rt></ruby> 围绕一套独特的流程和价值观构建，以确保其开放性（译者注：以下简称ASF）。
|
||||
![Wide open sky and trees][1]
|
||||
|
||||
作为 ASF[2] 的长期志愿者和导师（以及现任董事会成员）和 Apache 孵化器的副总裁，我很自豪能够提供我对 ASF 运营的独特流程和价值观的见解。
|
||||
|
||||
以自由和实用的开源 [Apache 许可证][3] 为中心，ASF 的运营方式与许多其他基金会不同，因为它是一个为公共利益而建立的慈善组织。例如，ASF 董事会由成员选举产生。没有人可以购买董事会席位，ASF 是与个人而不是公司相关联的。一般来说，参与 ASF 的任何个人的公司隶属关系都不会被说明，这并不重要。结果是，ASF 营造了一个供应商中立的环境，公司可以在其中舒适地协作构建有价值的项目。
|
||||
|
||||
让我们看一下 ASF 如何选择其项目，开源许可证的现状以及你对 ASF 未来的展望。
|
||||
### Apache 孵化器流程和 Apache 方式
|
||||
|
||||
潜在的 Apache 项目始于 [Apache孵化器][4]，在那里它们接受帮助和指导，以期望能够毕业成为顶级的 Apache 项目。任何人都可以为孵化器制定项目提案（他们只需要找到 ASF 内部愿意帮助支持它的人）。在审查潜在的项目时，ASF 更愿意看到各种各样的人和实体参与其中——当然不只是一个单一的法人团体。我们发现，这种更广泛的多样性会导致项目被更广泛地使用并具有更长久的生命力。
|
||||
|
||||
孵化器的主要目的是帮助项目按照我们所说的 [Apache方式][5] 学习和运作。这是一套为社区主导的发展提供最佳实践的价值观。Apache 方式的最重要方面包括严格的供应商中立性和强大的社区的优先级，甚至优先于项目代码的强度。开放和透明的交流也是至关重要的：ASF 要求所有项目交流都是公开可访问的，并永久归档以支持异步协作。此外，开源的 Apache 许可证附加在所有被接受的项目上，确保所有源代码也是公开可用的。
|
||||
|
||||
在孵化器中，我们首先会根据项目与 Apache 价值观的一致程度来考察项目是否适合。不需要百分之百的一致，但项目需要愿意适应。还将从许可角度讨论确保项目与 Apache 完全兼容，在某些情况下，将根据需要删除或替换依赖项。Apache 方式会朝构建自我维持的社区方向做准备。也就是说，对于一些项目来说，建立社区可能很困难，那么这些项目将无法通过孵化器。
|
||||
|
||||
Apache 方式的另一个关键元素——对繁荣社区至关重要——是基于共识做出决策。根据我们的经验，开放讨论和避免单个项目负责人对该流程至关重要。我们有几个孵化项目，其中包括一个试图保持控制权的个性很强的人，但由于这个原因，这些项目没有成功。
|
||||
|
||||
### 开源和 Apache 许可证
|
||||
|
||||
开源项目有很多种。同时，使用开源许可证不会自动使项目开源。项目的社区才是释放开源的益处并促进更大开放和透明度的关键。
|
||||
|
||||
最近，一些公司高调地从 Apache 许可转向宽松许可。如果你的公司从开源许可证更改为非开源许可证，我不得不质疑你们当初为什么要选择开源许可证。这可能意味着商业模式不适合开源。我相信，通过改变开源许可证，公司正在对他们的社区和用户造成巨大的伤害。
|
||||
|
||||
正如我所说，ASF 是一个非营利性慈善组织，致力于为公众利益开发软件。这就是宽容的 Apache 许可证的目的。从该软件中赚钱很好，但这不是 Apache 许可证的目的。通常，ASF 不允许任何使用领域限制。_任何人_ 都可以以任何理由使用 Apache 项目。真正开源背后的理念是一些使用项目的人会回馈它，但绝对不能要求贡献。那些似乎困扰于这一点的公司需要明白，这不是开源的运作方式，也不是它应该的运作方式。
|
||||
|
||||
### 开源和 ASF 的未来
|
||||
|
||||
在过去的五到十年里，开源无疑得到了广泛的采用，尤其是在企业中加速采用。我可以肯定地说，地球上几乎没有哪个软件不包含或不依赖某种方式的开源项目。这种采用率只会增长。
|
||||
|
||||
与某些基金会不同，ASF 在项目招募方面相当放手。期待 ASF 能一如既往地坚持下去，阐明 Apache 方式的价值，并与那些在 ASF 方法中看到价值的项目合作。随着 ASF 项目在重大行业变革中处于领先地位（最初是 Web 服务器，最近是通过 Apache Hadoop 和 Spark、Cassandra 和 Kafka 等大数据项目），不干涉的做法已证明是成功和可持续的。
|
||||
|
||||
下一步，ASF 有几个大型的人工智能和机器学习项目。此外，一些 <ruby>物联网<rt>IoT</rt></ruby> 项目也通过了 Apache 孵化器，其中几个可能会变得相当有影响力。展望未来，期待 ASF 将一如既往，引入一些主要行业参与者使用的非常成功的开源项目，以及其他小型项目，这些项目提供了至关重要的（如果有更多的利基市场的话）吸引力。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/6/apache-software-foundation
|
||||
|
||||
作者：[Justin Mclean][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[hanszhao80](https://github.com/hanszhao80)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/justin-mclean
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/nature_open_sky_tree.png?itok=2J79Futp (Wide open sky and trees)
|
||||
[2]: https://www.apache.org/
|
||||
[3]: https://www.apache.org/licenses/LICENSE-2.0
|
||||
[4]: https://incubator.apache.org/
|
||||
[5]: https://apache.org/theapacheway/
|
||||
Loading…
Reference in New Issue
Block a user