mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-16 22:42:21 +08:00
Merge pull request #7056 from cyleft/master
Launching an Open Source Project: A Free Guide
This commit is contained in:
Xingyu.Wang
GitHub
commit
e6a1d238dc
@ -1,87 +0,0 @@
|
||||
translating by CYLeft
|
||||
|
||||
Launching an Open Source Project: A Free Guide
|
||||
============================================================
|
||||
|
||||
|
||||
|
||||
Launching a project and then rallying community support can be complicated, but the new guide to Starting an Open Source Project can help.
|
||||
|
||||
Increasingly, as open source programs become more pervasive at organizations of all sizes, tech and DevOps workers are choosing to or being asked to launch their own open source projects. From Google to Netflix to Facebook, companies are also releasing their open source creations to the community. It’s become common for open source projects to start from scratch internally, after which they benefit from collaboration involving external developers.
|
||||
|
||||
Launching a project and then rallying community support can be more complicated than you think, however. A little up-front work can help things go smoothly, and that’s exactly where the new guide to[ Starting an Open Source Project][1] comes in.
|
||||
|
||||
This free guide was created to help organizations already versed in open source learn how to start their own open source projects. It starts at the beginning of the process, including deciding what to open source, and moves on to budget and legal considerations, and more. The road to creating an open source project may be foreign, but major companies, from Google to Facebook, have opened up resources and provided guidance. In fact, Google has[ an extensive online destination][2] dedicated to open source best practices and how to open source projects.
|
||||
|
||||
“No matter how many smart people we hire inside the company, there’s always smarter people on the outside,” notes Jared Smith, Open Source Community Manager at Capital One. “We find it is worth it to us to open source and share our code with the outside world in exchange for getting some great advice from people on the outside who have expertise and are willing to share back with us.”
|
||||
|
||||
In the new guide, noted open source expert Ibrahim Haddad provides five reasons why an organization might open source a new project:
|
||||
|
||||
1. Accelerate an open solution; provide a reference implementation to a standard; share development costs for strategic functions
|
||||
|
||||
2. Commoditize a market; reduce prices of non-strategic software components.
|
||||
|
||||
3. Drive demand by building an ecosystem for your products.
|
||||
|
||||
4. Partner with others; engage customers; strengthen relationships with common goals.
|
||||
|
||||
5. Offer your customers the ability to self-support: the ability to adapt your code without waiting for you.
|
||||
|
||||
The guide notes: “The decision to release or create a new open source project depends on your circumstances. Your company should first achieve a certain level of open source mastery by using open source software and contributing to existing projects. This is because consuming can teach you how to leverage external projects and developers to build your products. And participation can bring more fluency in the conventions and culture of open source communities. (See our guides on [Using Open Source Code][3] and [Participating in Open Source Communities][4]) But once you have achieved open source fluency, the best time to start launching your own open source projects is simply ‘early’ and ‘often.’”
|
||||
|
||||
The guide also notes that planning can keep you and your organization out of legal trouble. Issues pertaining to licensing, distribution, support options, and even branding require thinking ahead if you want your project to flourish.
|
||||
|
||||
“I think it is a crucial thing for a company to be thinking about what they’re hoping to achieve with a new open source project,” said John Mertic, Director of Program Management at The Linux Foundation. “They must think about the value of it to the community and developers out there and what outcomes they’re hoping to get out of it. And then they must understand all the pieces they must have in place to do this the right way, including legal, governance, infrastructure and a starting community. Those are the things I always stress the most when you’re putting an open source project out there.”
|
||||
|
||||
The[ Starting an Open Source Project][5] guide can help you with everything from licensing issues to best development practices, and it explores how to seamlessly and safely weave existing open components into your open source projects. It is one of a new collection of free guides from The Linux Foundation and The TODO Group that are all extremely valuable for any organization running an open source program.[ The guides are available][6]now to help you run an open source program office where open source is supported, shared, and leveraged. With such an office, organizations can establish and execute on their open source strategies efficiently, with clear terms.
|
||||
|
||||
These free resources were produced based on expertise from open source leaders.[ Check out all the guides here][7] and stay tuned for our continuing coverage.
|
||||
|
||||
Also, don’t miss the previous articles in the series:
|
||||
|
||||
[How to Create an Open Source Program][8]
|
||||
|
||||
[Tools for Managing Open Source Programs][9]
|
||||
|
||||
[Measuring Your Open Source Program’s Success][10]
|
||||
|
||||
[Effective Strategies for Recruiting Open Source Developers][11]
|
||||
|
||||
[Participating in Open Source Communities][12]
|
||||
|
||||
[Using Open Source Code][13]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linuxfoundation.org/blog/launching-open-source-project-free-guide/
|
||||
|
||||
作者：[Sam Dean ][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.linuxfoundation.org/author/sdean/
|
||||
[1]:https://www.linuxfoundation.org/resources/open-source-guides/starting-open-source-project/
|
||||
[2]:https://www.linux.com/blog/learn/chapter/open-source-management/2017/5/googles-new-home-all-things-open-source-runs-deep
|
||||
[3]:https://www.linuxfoundation.org/using-open-source-code/
|
||||
[4]:https://www.linuxfoundation.org/participating-open-source-communities/
|
||||
[5]:https://www.linuxfoundation.org/resources/open-source-guides/starting-open-source-project/
|
||||
[6]:https://github.com/todogroup/guides
|
||||
[7]:https://github.com/todogroup/guides
|
||||
[8]:https://github.com/todogroup/guides/blob/master/creating-an-open-source-program.md
|
||||
[9]:https://www.linuxfoundation.org/blog/managing-open-source-programs-free-guide/
|
||||
[10]:https://www.linuxfoundation.org/measuring-your-open-source-program-success/
|
||||
[11]:https://www.linuxfoundation.org/blog/effective-strategies-recruiting-open-source-developers/
|
||||
[12]:https://www.linuxfoundation.org/participating-open-source-communities/
|
||||
[13]:https://www.linuxfoundation.org/using-open-source-code/
|
||||
[14]:https://www.linuxfoundation.org/author/sdean/
|
||||
[15]:https://www.linuxfoundation.org/category/audience/attorneys/
|
||||
[16]:https://www.linuxfoundation.org/category/blog/
|
||||
[17]:https://www.linuxfoundation.org/category/audience/c-level/
|
||||
[18]:https://www.linuxfoundation.org/category/audience/developer-influencers/
|
||||
[19]:https://www.linuxfoundation.org/category/audience/entrepreneurs/
|
||||
[20]:https://www.linuxfoundation.org/category/content-placement/lf-brand/
|
||||
[21]:https://www.linuxfoundation.org/category/audience/open-source-developers/
|
||||
[22]:https://www.linuxfoundation.org/category/audience/open-source-professionals/
|
||||
[23]:https://www.linuxfoundation.org/category/audience/open-source-users/
|
||||
@ -0,0 +1,79 @@
|
||||
启动开源项目：免费指导！
|
||||
============================================================
|
||||
|
||||
|
||||
|
||||
启动项目、组建社区支持可能会比较复杂，但是这个全新的指南可以帮助你开启开源项目。
|
||||
|
||||
不同规模的组织、技术人员和 DecOps 工作者选择使用甚至被要求开发自己的开源项目，开源程序变得越来越普遍。从 Google 到 Netflix 再到 Facebook 的这些公司都在发布它们的开源创作到开源社区。一个开源项目由内部人员组织起来，再由外部开发人员合作，帮助丰富开源项目是很常见的。
|
||||
|
||||
不管怎样，在你看来开启一个开源项目、组建社区支持还是很复杂。一些前期准备可以帮助事情开展变得顺利，就是这个崭新且全新的开源项目指南 [ 启动一个开源项目 ][1]。
|
||||
|
||||
这个免费指南是为了帮助那些深谙开源的组织者启动自己的开源项目而诞生。在本文的开始，介绍包括了决定开源什么项目，预计项目费用，考虑开源协议和一些其他方面。开源项目这种方式可能源自国外，但是从 Google 到 Facebook 这样一些主要的开源公司都已经开放提供了开源项目指导资源。事实上，Google 拥有的 [ 丰富的在线地址 ][2] 在开源项目实践和启动开源项目上持续贡献。
|
||||
|
||||
Capital One 开源社区经理 Jared Smith 指出，“无论公司在内雇佣了多少聪明人，总还是有聪明人在公司之外”， “我们发现开放我们的源代码给外面世界的专业且愿意分享的人士交流经验是非常值得的，我们能从中获取一些非常好的建议”。
|
||||
|
||||
新指南中，开源专家 Ibrahim Haddad 提供了了五条关于一个组织为什么要在新项目中开放源代码的原因：
|
||||
|
||||
1. 促成开放式问题解决方案；提供标准参考成就；共享战略功能开发开销。
|
||||
|
||||
2. 商品化市场；减少非战略软件成本费用。
|
||||
|
||||
3. 建立产品生态，驱动需求。
|
||||
|
||||
4. 协同合作；吸引客户；深化共同目标间的关系。
|
||||
|
||||
5. 提供用户自我支持的能里：无需等待即可调整代码
|
||||
|
||||
本文指出：“做出开放或创建一个新的开源项目的决定和自身境况相关。你的公司应该在使用或贡献既存的开源项目上拥有一定程度的熟练度。这是因为消费能够指导你，通过外部工程使开发者对自己的产品构建变得省力（在我们的指南 [ 使用开源代码 ][3] 和 [ 加入开源社区 ][4] 上）。但是当一旦你顺利的参与过开源，那这将是启动你自己的开源项目的最佳时机”
|
||||
|
||||
这些免费的教程是基于专业的开源领导人而创作的。[ 在这里可以查看所有指南 ][7] 然后关注我们的后续报导。
|
||||
|
||||
也别错过了本系列早些的文章：
|
||||
|
||||
[ 如何创建开源程序 ][8]
|
||||
|
||||
[ 开源程序管理工具 ][9]
|
||||
|
||||
[ 衡量你的开源项目成功性 ][10]
|
||||
|
||||
[ 吸引开源开发者的高效策略 ][11]
|
||||
|
||||
[ 加入开源社区 ][12]
|
||||
|
||||
[ 使用开源代码 ][13]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linuxfoundation.org/blog/launching-open-source-project-free-guide/
|
||||
|
||||
作者：[Sam Dean ][a]
|
||||
译者：[译者ID](https://github.com/CYLeft)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.linuxfoundation.org/author/sdean/
|
||||
[1]:https://www.linuxfoundation.org/resources/open-source-guides/starting-open-source-project/
|
||||
[2]:https://www.linux.com/blog/learn/chapter/open-source-management/2017/5/googles-new-home-all-things-open-source-runs-deep
|
||||
[3]:https://www.linuxfoundation.org/using-open-source-code/
|
||||
[4]:https://www.linuxfoundation.org/participating-open-source-communities/
|
||||
[5]:https://www.linuxfoundation.org/resources/open-source-guides/starting-open-source-project/
|
||||
[6]:https://github.com/todogroup/guides
|
||||
[7]:https://github.com/todogroup/guides
|
||||
[8]:https://github.com/todogroup/guides/blob/master/creating-an-open-source-program.md
|
||||
[9]:https://www.linuxfoundation.org/blog/managing-open-source-programs-free-guide/
|
||||
[10]:https://www.linuxfoundation.org/measuring-your-open-source-program-success/
|
||||
[11]:https://www.linuxfoundation.org/blog/effective-strategies-recruiting-open-source-developers/
|
||||
[12]:https://www.linuxfoundation.org/participating-open-source-communities/
|
||||
[13]:https://www.linuxfoundation.org/using-open-source-code/
|
||||
[14]:https://www.linuxfoundation.org/author/sdean/
|
||||
[15]:https://www.linuxfoundation.org/category/audience/attorneys/
|
||||
[16]:https://www.linuxfoundation.org/category/blog/
|
||||
[17]:https://www.linuxfoundation.org/category/audience/c-level/
|
||||
[18]:https://www.linuxfoundation.org/category/audience/developer-influencers/
|
||||
[19]:https://www.linuxfoundation.org/category/audience/entrepreneurs/
|
||||
[20]:https://www.linuxfoundation.org/category/content-placement/lf-brand/
|
||||
[21]:https://www.linuxfoundation.org/category/audience/open-source-developers/
|
||||
[22]:https://www.linuxfoundation.org/category/audience/open-source-professionals/
|
||||
[23]:https://www.linuxfoundation.org/category/audience/open-source-users/
|
||||
Loading…
Reference in New Issue
Block a user