mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
translate done at 2017年 12月 25日 星期一 14:39:58 CST
This commit is contained in:
darksun
parent
4f144647c9
commit
1d5156c5ea
@ -1,71 +0,0 @@
|
||||
translating lujun9972
|
||||
Overcoming challenges when building great global communities
|
||||
======
|
||||
![配图][https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BUSINESS_community2.png?itok=1blC7-NY]
|
||||
|
||||
Today's open source communities include people from all around the world. What challenges can you expect when establishing an online community, and how can you help overcome them?
|
||||
|
||||
People contributing to an open source community share a commitment to the software they're helping to develop. In the past, people communicated by meeting in person at a set place and time, or through letters or phone calls. Today, technology has fostered growth of online communities--people can simply pop into a chat room or messaging channel and start working together. You might work with someone in Morocco in the morning, for example, and with someone in Hawaii that evening.
|
||||
|
||||
## Global communities: 3 common challenges
|
||||
|
||||
Anyone who's ever worked in a group knows that differences of opinion can be difficult to overcome. In online communities, language barriers, different time zones, and cultural differences can also create challenges.
|
||||
|
||||
### Language barriers
|
||||
|
||||
English is the predominant language in open source communities, so people without strong English language skills may find it difficult to understand documentation or suggest changes. To overcome this problem and attract community members from other areas, invite bilingual people into your community. Ask around--you might be surprised by who is fluent in other languages. Bilingual community members can help others contribute by helping to bridge language barriers, and can help your project engage with a wider audience by translating software and documentation.
|
||||
|
||||
People also program in different languages. You might prefer working in Bash, for example, while others prefer Python, Ruby, C, and so on. This also means that people might find it difficult to contribute to your codebase because of the programming language. It is important for project leaders to choose a language that's been adopted by the software community in general. If you choose a less-used programming language, fewer people will participate.
|
||||
|
||||
### Different time zones
|
||||
|
||||
Time zones can present another challenge to open source communities. For example, if you are in San Francisco and want to schedule a video call with a member who is in London, you'll need to adjust for an 8-hour time difference. You may need to work very late or early, depending on the locations of your colleagues.
|
||||
|
||||
Physical sprints, in which your team works together in the same time zone, can help address this challenge, but few communities can afford this option. Schedule regular virtual meetings to discuss your projects, and establish a regular time and place where everyone can discuss pending issues, upcoming releases, and other topics.
|
||||
|
||||
Different time zones can also work to your advantage because team members can work around the clock. If you have a real-time communication platform such as IRC, users can find someone to answer their questions at any time of the day or night.
|
||||
|
||||
### Cultural differences
|
||||
|
||||
Cultural differences can be one of the greatest challenges for open source communities. People from different parts of the world have different ways of thinking, planning, and solving problems. Political situations can also affect work environments and influence decisions.
|
||||
|
||||
As a project leader, you should strive to build an environment of tolerance for different perspectives. Cultural differences can encourage discussion among the community. Constructive discussions are always good for projects because they help community members see different angles of the same topic. Different opinions also help improve problem solving.
|
||||
|
||||
To succeed in open source, your team must learn to embrace differences. This is not always easy, but diversity will ultimately benefit your community.
|
||||
|
||||
## Additional ways to strengthen online communities
|
||||
|
||||
**Go local:** Online community members may discover contributors who are located nearby--meet up and start a local community. Two people are all you need to start a community. Invite other users and employees at local companies; they might even offer space for future meetups.
|
||||
|
||||
**Find or plan events:** Hosting events is a great, inexpensive way to build a local community. Get together at a local coffee shop or brewery to celebrate the newest version release or the implementation of a core feature. The more events you host, the more people will likely join you (even if just out of curiosity). Eventually, a company may offer you space for meetups, or you can raise funds to cover your expenses.
|
||||
|
||||
**Keep in touch:** After each event, reach out to local community members. Collect email addresses or other contact information, and ask them to join your chat platform. Invite them to contribute to the wider community. You will likely discover lots of local talent, and who knows--you might even find your next core developer!
|
||||
|
||||
**Share your experiences:** Your local community is a valuable resource, not only for you, but also for the wider community. Share your findings and experiences with others who might benefit from them. If you're sure how to start planning an event or a meetup, ask others for their insights. Chances are someone out there has experience that can help get you on the right track.
|
||||
|
||||
**Consider cultural differences:** Remember that cultural norms vary by location and population, so scheduling a particular event in the early morning might be fine for people in one location, for example, but inappropriate for people in another. Of course, you can--and should--use references from the wider community to gain a better understanding of such differences, but you will sometimes need to experiment through trial and error. Don't forget to share what you learn so others can benefit from your experience.
|
||||
|
||||
**Check your personal views:** Avoid airing strong opinions (especially regarding politics) in the work environment. This will only inhibit open communication and problem-solving. Instead, focus on engaging in constructive discussion with team members. If you do find yourself in a heated argument, take a step back, cool down, and refocus the discussion in a more positive direction. Discussions should always be constructive, and different perspectives should benefit your community. Never put your personal views before the community 's greater good.
|
||||
|
||||
**Try asynchronous communication:** Real-time chat platforms are on everyone's radar these days, but don't forget email. If you can't find someone in your online platform, send them an email. Chances are you'll get a quick reply. Consider emerging platforms that focus on async communications, such as [Twist][1], and don't forget to check and update forums and wikis.
|
||||
|
||||
**Try different solutions:** There's no single perfect formula, and the most effective way to learn is often through experience. Trial and error can teach you a lot. Do not be afraid to fail; you will learn from failure and you can never stop improving.
|
||||
|
||||
## Communities require nurturing
|
||||
|
||||
Think of your community as a small plant. Each day you must water it and make sure it gets sunlight and oxygen. Take the same approach to your communities: Listen to your contributors, and remember that you are dealing with human beings who need to be in constant communication to function properly. If your community loses the human touch, people will stop contributing to it.
|
||||
|
||||
Finally, keep in mind that every community is different, and no single solution will ever apply to all of them. Be persistent and never stop learning from your community, and then adapt.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/17/12/working-worldwide-communities
|
||||
|
||||
作者：[José Antonio Rey][a]
|
||||
译者：[lujun9972](https://github.com/lujun9972)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/jose
|
||||
[1]:https://twistapp.com
|
||||
@ -0,0 +1,70 @@
|
||||
构建全球社区带来的挑战
|
||||
======
|
||||
|
||||
|
||||
今天的开源组织参与人员来自于全世界. 你能预见到组建在线社区可能遇到哪些困难吗？有没有什么办法能够克服这些困难呢?
|
||||
|
||||
为开源社区贡献力量的人共同合作推动软件的开发和发展(People contributing to an open source community share a commitment to the software they're helping to develop). 在过去, 人们是面对面或者通过邮件和电话来交流的. 今天, 科技孕育出了在线交流--人们只需要进入一个聊天室或消息渠道就能一起工作了. 比如，你可以早上跟摩洛哥的人一起工作，到了晚上又跟夏威夷的人一起工作.
|
||||
|
||||
## 全球社区的三个挑战
|
||||
|
||||
任何一个团队合作过的人都知道意见分歧是很难被克服的. 对于在线社区来说, 语言障碍, 不同的时区, 以及文化差异也带来了新的挑战.
|
||||
|
||||
### 语言障碍
|
||||
|
||||
英语是开源社区中的主流语言, 因此英语不好的人会很难看懂文档和修改意见. 为了克服这个问题，吸引其他地区的社区成员,你需要邀请双语者参与到社区中来. 问问周围的人--你会发现意想不到的精通其他语言的人. 社区的双语成员可以帮助别人跨越语言障碍, 并且可以通过翻译软件和文档来扩大项目的受众范围.
|
||||
|
||||
人们使用的编程语言也不一样. 你可能喜欢用Bash而其他人则可能更喜欢 Python, Ruby, C 等其他语言. 这意味着，人们可能由于编程语言的原因而难以为你的代码库做贡献. 项目负责人为项目选择一门被软件社区广泛认可的语言至关重要. 如果你选择了一门偏门的语言, 则很少人能够参与其中.
|
||||
|
||||
### 不同的时区
|
||||
|
||||
时区为开源社区带来了另一个挑战. 比如, 若你在芝加哥，想与一个在伦敦的成员安排一次视频会议, 你需要调整8小时的时差. 根据合作者的地理位置，你可能要在深夜或者清晨工作.
|
||||
|
||||
肉体转移(Physical sprints),让你的团队在同一个时区工作可以帮助克服这个挑战, 但这中方法只有极少数社区才能够负担的起. 我们还可以定期举行虚拟会议讨论项目, 建立一个固定的时间和地点以供所有人来讨论未决的事项, 即将发布的版本等其他主题.
|
||||
|
||||
不同的时区也可以成为你的优势，因为团队成员可以全天候的工作. 若你拥有一个类似 IRC 这样的实时交流平台, 用户可以在任意时间都能找到人来回答问题.
|
||||
|
||||
### 文化差异
|
||||
|
||||
文化差异是开源组织面临的最大挑战. 世界各地的人都有不同的思考方式, 计划以及解决问题的方法. 政治环境也会影响工作环境并影响决策.
|
||||
|
||||
作为项目负责人, 你应该努力构建一种能包容不同看法的环境. 文化差异可以鼓励社区沟通. 建设性的讨论总是对项目有益,因为它可以帮助社区成员从不同角度看待问题. 不同意见也有助于解决问题.
|
||||
|
||||
要成功开源, 团队必须学会拥抱差异. 这不简单, 但多样性最终会使社区收益.
|
||||
|
||||
## 加强在线沟通的其他方法
|
||||
|
||||
**本地化:** 在线社区成员可能会发现位于附近的贡献者--去见个面并组织一个本地社区. 只需要两个人就能组建一个社区了. 可以邀请其他当地用户或雇员参与其中; 他们甚至还能为以后的聚会提供场所呢.
|
||||
|
||||
**组织活动:** 组织活动是构建本地社区的好方法,而且费用也不高. 你可以在当地的咖啡屋或者啤酒厂聚会，庆祝最新版本的发布或者某个核心功能的实现. 组织的活动越多, 人们参与的热情就越高(即使只是因为单纯的好奇心). 最终, 可能会找到一家公司为你提供聚会的场地,或者为你提供赞助.
|
||||
|
||||
**保持联系:** 每次活动后, 联系本地社区成员. 收起电子邮箱地址或者其他联系方式并邀请他们参与到你的交流平台中. 邀请他们为其他社区做贡献. 你很可能会发现很多当地的人才,运气好的话，甚至可能发现新的核心开发人员!
|
||||
|
||||
**分享经验:** 本地社区是一种非常有价值的资源, 对你，对其他社区来说都是. 与可能受益的人分享你的发现和经验. 如果你不清楚(译者注：这里原文是说sure，但是根据上下文，这里应该是not sure)如何策划一场活动或会议, 可以咨询其他人的意见. 也许能找到一些有经验的人帮你走到正轨.
|
||||
|
||||
**关注文化差异:** 记住，文化规范因地点和人口而异, 因此在清晨安排某项活动可能适用于一个地方的人，但是不合适另一个地方的人. 当然, 你可以--也应该--利用其他社区的参考资料来更好地理解这种差异性, 但有时你也需要通过试错的方式来学习. 不要忘了分享你所学到的东西，让别人也从中获益.
|
||||
|
||||
**检查个人观点:** 避免在工作场合提出带有很强主观色彩的观点(尤其是与政治相关的观点). 这会抑制开放式的沟通和问题的解决. 相反,应该专注于鼓励与团队成员展开建设性讨论. 如果你发现陷入了激烈的争论中, 那么后退一步,冷静一下, 然后再从更加积极的角度出发重新进行讨论. 讨论必须是有建设性的,从多个角度讨论问题对社区有益. 永远不要把自己的主观观念放在社区的总体利益之前.
|
||||
|
||||
**尝试异步沟通:** 这些天，实时通讯平台已经引起了大家的关注, 但除此之外还别忘了电子邮件. 如果没有在网络平台上找到人的话，可以给他们发送一封电子邮件. 有可能你很快就能得到回复. 考虑使用那些专注于异步沟通的平台，比如 [Twist][1], 也不要忘了查看并更新论坛和维基.
|
||||
|
||||
**使用不同的解决方案:** 并不存在一个单一的完美的解决方法, 学习最有效的方法还是通过经验来学习. 从反复试验中你可以学到很多东西.不要害怕失败; 你慧聪失败中学到很多东西从而不停地进步.
|
||||
|
||||
## 社区需要营养
|
||||
|
||||
将社区想象成是一颗植物的幼苗. 你需要每天给它浇水，提供阳光和氧气. 社区也是一样: 倾听贡献者的声音, 记住你在与活生生的人进行互动，他们需要以合适的方式进行持续的交流. 如果社区缺少了人情味, 人们会停止对它的贡献.
|
||||
|
||||
最后, 请记住，每个社区都是不同的, 没有一种单一的解决方法能够适用于所有社区. 坚持不断地从社区中学习并适应这个社区.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/17/12/working-worldwide-communities
|
||||
|
||||
作者：[José Antonio Rey][a]
|
||||
译者：[lujun9972](https://github.com/lujun9972)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/jose
|
||||
[1]:https://twistapp.com
|
||||
Loading…
Reference in New Issue
Block a user