mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-13 22:30:37 +08:00
geekpi
GitHub
commit
85367b4944
@ -1,77 +0,0 @@
|
||||
translating----geekpi
|
||||
|
||||
5 ways to expand your project's contributor base
|
||||
============================================================
|
||||
|
||||
|
||||
Image by :
|
||||
|
||||
opensource.com
|
||||
|
||||
So many free and open source software projects were started to solve a problem, and people began to contribute to them because they too wanted a fix to what they encountered. End users of the project find it useful for their needs, and the project grows. And that shared purpose and focus attracts people to a project's community.
|
||||
|
||||
Like anything with a lifespan, growth is both a sign of and the source of a project's viability. So how do project leads and maintainers encourage the growth of the contributor base? Here are five ways.
|
||||
|
||||
### 1\. Provide good documentation
|
||||
|
||||
People often underestimate the importance of the [documentation][2] of a project. It is the primary source of information for a project's contributors, and it motivates their efforts. The information has to be correct and current. It should include steps for how to build the software, for how to submit patches, a coding style guide, and more.
|
||||
|
||||
Check out the [7 rules for creating world class documentation][3] from long-time tech writer and editor Bob Reselman.
|
||||
|
||||
A good example of developer documentation is the [Python Developer's Guide][4]. It includes clear and concise steps that cover every aspect of Python development.
|
||||
|
||||
### 2\. Provide easy entry points
|
||||
|
||||
If your project has an [issue or bug tracker][5], make sure to mark the beginner-level tasks as an "easy bug" or a "starting point." New contributors can easily hop on board by tackling these issues. The tracker is also the place for marking nonprogramming tasks like graphic design, artwork, and documentation improvements. There are many project members who do not code every day, but who nevertheless become a driving force by contributing through such means.
|
||||
|
||||
The Fedora Project maintains one such [easy fix or entrance tracker][6].
|
||||
|
||||
### 3\. Provide regular feedback for patches
|
||||
|
||||
Acknowledge every patch, even if it is a single line, and give feedback to the author. Providing feedback helps engage prospective candidates and guides them as they acquaint themselves with the project. All projects should have a mailing list and [a chat function][7] for communication. Q&A sessions can happen in these mediums. Most projects do not become successful overnight, but those that thrive have lists and communications channels that create an environment that supports growth.
|
||||
|
||||
### 4\. Promote your project
|
||||
|
||||
A project started to solve a problem can actually turn out to be useful for others in development as well. As a primary contributor to the project, your responsibility is to document your project and promote it. Write blog posts, and share the project's progress on social media. You can have a short description of how to get started as a contributor to the project and in that description provide a reference to the main developer documentation. In addition, be sure to provide information on roadmaps and future releases.
|
||||
|
||||
Get [tips on writing][8] for your audience from Rikki Endsley, community manager for Opensource.com.
|
||||
|
||||
### 5\. Be welcoming
|
||||
|
||||
A friendly conversational tone with prompt replies will bolster a person's interest in your project. Initially, the questions will be only for help, but in the future new contributors may also come up with ideas or suggestions. Enable them with the confidence that they can become a contributor to the project.
|
||||
|
||||
Remember that you are being judged. People observe how developers of any project talk with each other on a mailing list or on chat. These are indicators of how welcoming and open people are to new contributors. When working with technology, we sometimes forget the human touch, but this is important for any project's ecosystem. Consider a case where a project is the best, but the project maintainer is not very welcoming. This manager may drive users away from the project. With a large user base, an unsupportive environment may fracture and a group of users may decide to fork and start a new project. There are successful examples of such incidents in the open source world.
|
||||
|
||||
Also, for the consistent growth and flow of ideas on an open source project, it's important to have people from varying backgrounds.
|
||||
|
||||
Finally, the project owner has the responsibility to sustain and help grow the project. Coaching new contributors is essential for the project, and they will turn out to be future leaders for the project and the community.
|
||||
|
||||
Read: _[7 ways to make new contributors feel welcome][1]_ by Nicole Engard, a content strategist at Red Hat.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
|
||||
|
||||
Kushal Das - Kushal Das is a CPython Core Developer and director at Python Software Foundation. He is a long-time FOSS contributor, and mentor, who helps first-time contributors to step into the world of contributions. He is currently working as Fedora Cloud Engineer at Red Hat. He blogs at https://kushaldas.in. You can also find him at Twitter @kushaldas
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/17/1/expand-project-contributor-base
|
||||
|
||||
作者：[Kushal Das][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/kushaldas
|
||||
[1]:https://opensource.com/life/16/5/sumana-harihareswara-maria-naggaga-oscon
|
||||
[2]:https://opensource.com/tags/documentation
|
||||
[3]:https://opensource.com/business/16/1/scale-14x-interview-bob-reselman
|
||||
[4]:https://docs.python.org/devguide/
|
||||
[5]:https://opensource.com/tags/bugs-and-issues
|
||||
[6]:https://fedoraproject.org/easyfix/
|
||||
[7]:https://opensource.com/alternatives/slack
|
||||
[8]:https://opensource.com/business/15/10/what-stephen-king-can-teach-tech-writers
|
||||
@ -0,0 +1,75 @@
|
||||
5 个扩展你项目贡献者基础的方法
|
||||
============================================================
|
||||
|
||||
|
||||
图片提供
|
||||
|
||||
opensource.com
|
||||
|
||||
许多自由和开源软件项目开始解决一个问题时，就人们开始为它们贡献，因为他们也想修复他们遇到的问题。当项目的最终用户发现它对他们的需求有用，项目就开始增长。这种共同的目的和焦点吸引人们到同一个项目社区。
|
||||
|
||||
像任何事物都是有寿命的，增长即是标志也是项目成功的来源。那么项目领导和维护者如何鼓励贡献者基数的增长？这里有五种方法。
|
||||
|
||||
### 1. 提供好的文档
|
||||
|
||||
人们经常低估项目[文档][2]的重要性。它是项目贡献者的主要信息来源，它会激励他们努力。信息必须是正确和最新的。它应该包括如何构建软件、如何提交补丁、编码风格指南等步骤。
|
||||
|
||||
查看长期科技作家和编辑的 Bob Reselman 的[ 7 个创建世界级文档的规则][3]。
|
||||
|
||||
开发人员文档的一个很好的例子是[ Python 开发人员指南][4]。它包括清晰简洁的步骤，涵盖 Python 开发的各个方面。
|
||||
|
||||
### 2. 提供简单入口
|
||||
|
||||
如果你的项目有[问题或 bug 追踪][5]，请确保将初级任务标记为一个“容易 bug ”或“起点”。新的贡献者可以很容易地通过解决这些问题进入项目。追踪器也是标记非编程任务（如平面设计、图稿和文档改进）的地方。有许多项目成员不是每天都编码，但是却通过这种方式成为推动力。
|
||||
|
||||
Fedora 项目维护一个这样的[轻松修复或入口跟踪][6]。
|
||||
|
||||
### 3. 为补丁提供常规反馈
|
||||
|
||||
即使它是一行，也要确认每个补丁，并给作者反馈。提供反馈有助于吸引潜在的候选人，并指导他们熟悉项目。所有项目都应有一个邮件列表和[聊天功能][7]进行通信。问答可在这些媒介中发生。大多数项目不会在一夜之间成功，但那些繁荣的列表和沟通渠道创造一个支持增长的环境。
|
||||
|
||||
### 4. 推广你的项目
|
||||
|
||||
开始解决问题的项目实际上可能对其他开发人员也有用。作为项目的主要贡献者，你的责任是写下你的的项目并推广它。写博客文章，并在社交媒体上分享项目的进展。你可以简要描述如何作为项目的贡献者开始使用，并在该描述中提供对主要开发者文档的参考。此外，请务必提供有关路线图和未来版本的信息。
|
||||
|
||||
获取 Opensource.com 的社区经理 Rikki Endsley 的获得你的听众的[写作提示][8]。
|
||||
|
||||
### 5. 保持友好
|
||||
|
||||
友好的对话语调和迅速的回复将加强人们对你的项目的兴趣。最初，问题只是为了寻求帮助，但在未来新的贡献者也可能会提出想法或建议。使他们有信心他们可以成为项目的贡献者。
|
||||
|
||||
记住你一直再被评判。人们会观察任何项目开发者如何在邮件列表或聊天上的交谈。这些意味着对新贡献者的欢迎和开放。当使用技术时，我们有时忘记人们，但这对于任何项目的生态系统都很重要。考虑一个情况，项目是很好的，但项目维护者不是很受欢迎。该管理员可能会驱使用户远离项目。对于有大量用户基数的项目而言，不被支持的环境可能导致分裂，一组用户可能决定 fork 并启动新项目。在开源世界中有这样的成功例子。
|
||||
|
||||
另外，对于持续增长以及对项目不断的点子，拥有来自不同背景的人是很重要的。
|
||||
|
||||
最后，项目主人有责任维持和帮助项目成长。指导新的贡献者是项目的关键，他们将成为项目和社区的未来领导者。
|
||||
|
||||
阅读：由红帽的内容战略家 Nicole Engard 写的_[ 7 种方式让新的贡献者感到受欢迎][1] _。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
|
||||
|
||||
Kushal Das - Kushal Das 是 Python 软件基金会的一名 CPython 核心开发人员和主管。他是一名长期的 FOSS 贡献者和导师，他帮助新人进入贡献世界。他目前在 Red Hat 担任 Fedora 云工程师。他的博客在 https://kushaldas.in。你也可以在 Twitter @kushaldas 上找到他
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/17/1/expand-project-contributor-base
|
||||
|
||||
作者：[Kushal Das][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/kushaldas
|
||||
[1]:https://opensource.com/life/16/5/sumana-harihareswara-maria-naggaga-oscon
|
||||
[2]:https://opensource.com/tags/documentation
|
||||
[3]:https://opensource.com/business/16/1/scale-14x-interview-bob-reselman
|
||||
[4]:https://docs.python.org/devguide/
|
||||
[5]:https://opensource.com/tags/bugs-and-issues
|
||||
[6]:https://fedoraproject.org/easyfix/
|
||||
[7]:https://opensource.com/alternatives/slack
|
||||
[8]:https://opensource.com/business/15/10/what-stephen-king-can-teach-tech-writers
|
||||
Loading…
Reference in New Issue
Block a user