mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
Merge pull request #25515 from PeterPan0106/master
[提交译文]How to make community recognition more inclusive
This commit is contained in:
Xingyu.Wang
GitHub
commit
ec52bb8c54
@ -1,72 +0,0 @@
|
||||
[#]: subject: "How to make community recognition more inclusive"
|
||||
[#]: via: "https://opensource.com/article/22/5/inclusive-community-recognition"
|
||||
[#]: author: "Ray Paik https://opensource.com/users/rpaik"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "PeterPan0106"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
How to make community recognition more inclusive
|
||||
======
|
||||
Look beyond metrics to ensure that all contributions are valued. When everyone feels like they have a home where they're appreciated, community members will be encouraged to stay engaged.
|
||||
|
||||
![Global citizens unite to improve housing with open design and development][1]
|
||||
（Image by: Opensource.com）
|
||||
|
||||
Giving recognition to someone for a job well done is one of my favorite duties as a community manager. Not only do I get to thank someone, but I also have a chance to highlight a role model for the rest of the community. Recognition also provides an opportunity to celebrate an achievement, like someone helping new community members with onboarding, reducing technical debt, or contributing an exciting new feature.
|
||||
|
||||
However, the methods used to identify contributions and recognize them can have unintended consequences. For example, sometimes community managers use charts like the following during recognitions, emphasizing pull requests (PRs) and contributions to code repositories.
|
||||
|
||||
![A bar graph ranking 15 contributors according the the number of PRs merged in a year, ranging from 250 at the top to 50 at the bottom.][2]
|
||||
（Image by: Ray Paik, CC BY-SA 4.0）
|
||||
|
||||
![A bar graph ranking 10 contributing organizations by number of contributions, ranging from more than 15 to less than 5][3]
|
||||
（Image by: Ray Paik, CC BY-SA 4.0）
|
||||
|
||||
Three problems arise with using these types of data for recognition. First, there's too much focus on contributions in code repositories. In the early days, open source projects attracted mostly developers, so naturally a lot of collaboration was done around code. Now, an increasing number of nondevelopers are participating in communities (for example, through user groups, meetups, user-generated content), and they will be doing most of their work outside repositories. Those contributions don't register on a chart like *Annual Merged PRs*.
|
||||
|
||||
Second, with too much focus on metrics (that is, things that can be measured quantitatively), you may end up rewarding quantity over quality—or even impact. In the *Top Contributing Orgs* chart above, larger organizations have a clear advantage over smaller organizations, as they have more people available. By recognizing larger organizations for their volume of work or contributions, you may inadvertently make people from smaller organizations feel disenfranchised.
|
||||
|
||||
Finally, even though it's not the intent, some people may view these data as a ranking of the importance of individual community members or organizations.
|
||||
|
||||
For all these reasons, it's best to avoid relying solely on metrics for community recognition.
|
||||
|
||||
### Make recognition more meaningful
|
||||
|
||||
What are some more inclusive ways to approach community recognition and acknowledge a variety of contribution types? Communication channels like Discord, Internet Relay Chat (IRC), mailing lists, or Slack provide good clues as to which community members are active and what they're passionate about. For example, I'm always amazed to find members who are very generous in answering others' questions and helping newcomers. These contributions don't show up in community dashboards, but it's important to recognize this work and let everyone know that this contribution is valued.
|
||||
|
||||
Speaking of community dashboards, they're certainly important tools in open source communities. However, I caution against spending too much time building dashboards. Sooner or later, you will find that not everything is easily measurable, and even if you find a way to quantify something, it often lacks context.
|
||||
|
||||
One of the things I do to get more context around the contributions is to schedule coffee chats with community members. These conversations give me an opportunity to learn about why they decided to make the contribution, how much work was involved, others who were also involved, and so on.
|
||||
|
||||
When I talk to these members for the first time, I often hear that they feel it's important to find ways to give back to the community, and they're looking for ways to help. Some are even apologetic because they cannot contribute code, and I have to reassure them that code is no longer the only thing that matters in open source. Sometimes these conversations allow me to make connections among community members in the same city or industry, or to find other common interests. Fostering these connections helps strengthen a sense of belonging.
|
||||
|
||||
### Make recognition more impactful
|
||||
|
||||
In addition to finding more activities to recognize, you can also present recognition in ways that have a bigger effect. For example, be timely with kudos when you see a good contribution. A quick DM with a simple thank you can be more effective than something more formal a month or two later. Many people, myself included, tend to stress over sending the right merchandise with recognition, but it's important to remember that swag is not the main motivator for community members' contributions. Recognizing good work and making an effort to reach out goes a long way in making people feel appreciated.
|
||||
|
||||
It's also a good idea to give members an opportunity to participate in the recognition process. Once a community reaches a certain size, it's difficult to know everything that's happening. Having a simple nomination form that community members can submit will raise awareness of good contributions that others may not have been aware of. If your community has formal awards for members—for example, awards presented at an annual conference or meetups—involve members in the nomination and voting process. This not only provides an opportunity for more people to participate in the process, but the awards will also be more meaningful to recipients since they come from their peers.
|
||||
|
||||
Finally, giving recognition is a vital opportunity to get to know community members and build relationships. Sometimes the recognition process can feel almost transactional: "You did X, so we're going to award you with Y." Taking the time to do personal outreach along with the award will make community members feel more appreciated and strengthen their sense of belonging.
|
||||
|
||||
### Recognitions build community health
|
||||
|
||||
There's a lot of work to be done to improve diversity, inclusion, and belonging in open source communities. Better community recognitions play an essential role in these efforts. Ensuring that all contributions are valued and that everyone feels like they have a home where they're appreciated will encourage members to stay engaged in the community.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/5/inclusive-community-recognition
|
||||
|
||||
作者：[Ray Paik][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[PeterPan0106](https://github.com/PeterPan0106)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/rpaik
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/world_hands_diversity.png
|
||||
[2]: https://opensource.com/sites/default/files/2022-04/annual%20merged%20PRs.png
|
||||
[3]: https://opensource.com/sites/default/files/2022-04/top%20contributing%20orgs.png
|
||||
@ -0,0 +1,72 @@
|
||||
[#]: subject: "How to make community recognition more inclusive"
|
||||
[#]: via: "https://opensource.com/article/22/5/inclusive-community-recognition"
|
||||
[#]: author: "Ray Paik https://opensource.com/users/rpaik"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "PeterPan0106"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
如何使社区认可更加包容
|
||||
======
|
||||
抛开具体的工作量，我们认为所有的贡献都弥足珍贵。当所有社区贡献者都能获得家庭般的赞赏时，他们会更倾向于继续为社区添砖加瓦。
|
||||
|
||||
![Global citizens unite to improve housing with open design and development][1]
|
||||
（图源： Opensource.com）
|
||||
|
||||
给予一个优秀的工作足够的认同和赞赏是我作为一个社区管理员最喜欢的事。我不但有机会能够对贡献者表示感激，同时还能为社区设立一个优秀的榜样。认同和赞赏可以是为了庆祝一个成就，例如有人帮助其他成员加入社区、减少技术债务或者贡献了激动人心的新功能。
|
||||
|
||||
但是，用来确定贡献量的规则可能会有难以预料的后果。例如某些社区管理员利用如下图所示的图表来表彰贡献，过度地强调了pull requests以及对代码库的贡献量。
|
||||
|
||||
![A bar graph ranking 15 contributors according the the number of PRs merged in a year, ranging from 250 at the top to 50 at the bottom.][2]
|
||||
（图源： Ray Paik, CC BY-SA 4.0）
|
||||
|
||||
![A bar graph ranking 10 contributing organizations by number of contributions, ranging from more than 15 to less than 5][3]
|
||||
（图源： Ray Paik, CC BY-SA 4.0）
|
||||
|
||||
使用这样的方法进行表彰会产生三个问题。首先，这样过度聚焦了对代码库的贡献。早年间，开源项目主要吸引开发者参与，所以自然而然许多贡献是围绕代码的。现在，越来越多的非开发者正在积极参与社区项目（例如通过用户组、会议和用户本身生产的内容），他们的大多数贡献在代码库以外的地方。这些贡献将不会出现在诸如*年度合并PR数量*这样的表格上。
|
||||
|
||||
其次，过度聚焦贡献指标（指那些易于用数字统计的），最终会演变为更大的数量甚至超越了更好的质量甚至是影响力。在上图的*贡献组织排行榜*中，大型组织因为具有更多的可用人力，相对于小型组织就会有更为显著的优势。通过对大型组织在数量上的表彰将可能导致小型组织感到权利被剥夺了。
|
||||
|
||||
最终，尽管本意并非如此，但许多人都会把这些数据看做对个人或组织影响力的排名。
|
||||
|
||||
基于此，我们最好避免仅仅通过指标数量来表彰对社区的贡献。
|
||||
|
||||
### 令社区表彰更有意义
|
||||
|
||||
如何让社区表彰更为包容并且能够覆盖不同的贡献形式呢？一些通信频道例如Discord、IRC、mailing list和Slack可以很好的表明一个成员的活跃度及其感兴趣的领域。例如每当我看到一些人热衷于解答问题或者帮助新用户时，我会十分开心。这些贡献并不会出现在社区的数据板上，但是让这些贡献得到应有的认同和感谢并广为人知是十分重要的。
|
||||
|
||||
社区数据板显然是开源社区重要的工具。但对于花费在建设数据板的时间上，我锱铢必较。迟早你会发现，不是所有的东西都可以有清晰的标准进行度量，即便你能够想出规则量化一件事，你也依然会发现这些规则具有局限性。
|
||||
|
||||
为了获取更多的关于贡献的信息，我经常会安排社区成员茶话会。这些对话经常能够告诉我他们做出贡献的原因、有多少工作量以及谁同时也参与进来了等等。
|
||||
|
||||
当我第一次与他们对话时，我经常听到他们提及找到回馈社区的方法十分重要，而他们也在寻找方法来提供力所能及的帮助。许多人甚至因不能在代码方面做出贡献而感到内疚，而我会向他们强调代码不再是开源唯一重要的东西。有时这些对话能让我有机会接触到同一城市或同一行业的社区成员，或者发现更多共同的兴趣点。维护这些关系将有助于提升归属感。
|
||||
|
||||
### 令社区表彰更具影响力
|
||||
|
||||
除了寻找更多的活动形式，我们也可以让这些活动以更具影响力的形式呈现。例如在看到优质贡献时及时赞美。一个快速的感谢回复会比一两个月之后的正式感谢更有效。许多人包括我自己，都会强调给予更为正式而合理的表彰和奖励，但我们应当谨记，奖励并非社区成员贡献的主要动力。认可好的工作并努力去接触贡献者会令贡献者感到受重视。
|
||||
|
||||
让其他成员参与到认可的过程中也是一个很好的主意。一旦社区达到了一定的规模，便很难事无巨细地知晓一切细节。如果引入一个成员提名机制则会很好地让大家注意到优秀的贡献。如果你的社区拥有十分正式的奖项，例如在年度会议或聚会上颁发的奖项，请让社区成员参与提名和投票。这不仅提供了成员参与进来的平台，也令这些来自成员投票的奖项更有意义。
|
||||
|
||||
最后给予认同和感谢也是一个认识成员并加深了解的重要机会。有时候颁奖仿佛在进行交易：“你做了X，所以我们给你颁发了Y”。多在介绍成员上花些时间，将令成员感到更受重视并加强归属感。
|
||||
|
||||
### 社区认可令社区更为健康
|
||||
|
||||
在提高开源社区的多样性、包容性和归属感方面，我们仍有许多工作亟待改善。更好的社区认可将在其中起着不可或缺的作用。确保所有的贡献都受到重视，让每一位贡献者都感到家庭般氛围和赞赏，将鼓励他们继续为社区贡献。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/5/inclusive-community-recognition
|
||||
|
||||
作者：[Ray Paik][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[PeterPan0106](https://github.com/PeterPan0106)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/rpaik
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/world_hands_diversity.png
|
||||
[2]: https://opensource.com/sites/default/files/2022-04/annual%20merged%20PRs.png
|
||||
[3]: https://opensource.com/sites/default/files/2022-04/top%20contributing%20orgs.png
|
||||
Loading…
Reference in New Issue
Block a user