mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
六开箱
GitHub
commit
5587100fcc
@ -1,111 +0,0 @@
|
||||
[#]: subject: "5 levels of transparency for open source communities"
|
||||
[#]: via: "https://opensource.com/article/22/2/transparency-open-source-communities"
|
||||
[#]: author: "Emilio Galeano Gryciuk https://opensource.com/users/egaleano"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "aREversez"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
5 levels of transparency for open source communities
|
||||
======
|
||||
Open source community managers need to apply these 5 levels of
|
||||
transparency to build a thriving open source community.
|
||||
![Person in a field of dandelions][1]
|
||||
|
||||
Managers of open source communities have to be aware of the 5 levels of transparency that they can provide. These 5 levels of transparency are important for building a thriving open source community.
|
||||
|
||||
This article describes each level, its goals, and why they are important. But first, I revisit why transparency is important for open source ecosystems.
|
||||
|
||||
### Why do open source ecosystems need transparency?
|
||||
|
||||
* Transparent communities inspire trust** **in each other, which greases the wheels of collaboration.
|
||||
* Communities work together and exchange messages in the open.
|
||||
* Open source work happens in a transparent way to avoid friction.
|
||||
* Community managers need to report to their stakeholders.
|
||||
* Showing communities what information is available about them is healthy and encourages trust.
|
||||
|
||||
|
||||
|
||||
### What are the 5 levels of transparency?
|
||||
|
||||
#### Transparency level 1: Publish source code
|
||||
|
||||
This level is about releasing source code under an [Open Source Initiative (OSI)-approved license][2] in a public-facing version control system like [Git][3].
|
||||
|
||||
The first level's goal is to establish** **an open source project.
|
||||
|
||||
* This level is self-evident as there would be no open source project without the source code.
|
||||
* At the core of an open source project is the source code that people engage with—licensed under an OSI-approved license.
|
||||
* A public version control system enables collaboration and allows everyone to analyze the project and understand the collaboration patterns.
|
||||
|
||||
|
||||
|
||||
#### Transparency level 2: Publish community guidelines
|
||||
|
||||
You publish documentation and resources on contributing at this level, and you organize special events to educate the community.
|
||||
|
||||
The second level's goal is to create and grow a community for an open source project.
|
||||
|
||||
* Building an active community requires more than** **just having a source code**.**
|
||||
* Being transparent about how a project works and how to contribute enables others to join a project**.**
|
||||
* Growing the community may involve** **running events and doing special activities for contributors.
|
||||
|
||||
|
||||
|
||||
#### Transparency level 3: Celebrate successes
|
||||
|
||||
Once you reach this level, it's important to share insights about the community and publish reports about the project's status.
|
||||
|
||||
The third level's goal is to celebrate successes and secure further support** **beyond the initial phase of the community.
|
||||
|
||||
* As open source communities grow, it becomes harder to know what's happening everywhere.
|
||||
* Being transparent about the activities in the community helps community members know that their contributions are being seen and valued.
|
||||
* At this level of transparency, the reporting and analytics** **are sporadic and without specific tooling.
|
||||
|
||||
|
||||
|
||||
#### Transparency level 4: Understand the pulse of the community
|
||||
|
||||
This level is all about listening to the community—keeping an eye on the project's evolution in community activity and the software development process to take corrective actions.
|
||||
|
||||
The fourth level's goal is to take the community to the next level by understanding its evolution and trajectory with consistency and scientific rigor.
|
||||
|
||||
* Reporting mechanisms and analytics tools help keep an eye on what is happening.
|
||||
* You can compare events in the community and the subsequent reactions of community members to a baseline and other events in the community.
|
||||
* Deeper insights into the community are possible with consistent listening.
|
||||
|
||||
|
||||
|
||||
#### Transparency level 5: Maintain the community long-term
|
||||
|
||||
The last step is acting on community metrics and improving community engagement.
|
||||
|
||||
The fifth level's goal is to make meaningful and impactful decisions about community engagement.
|
||||
|
||||
* Have systems in place to** **react to changes** **in community metrics.
|
||||
* Follow up on how changes to the community are showing up in the metrics and analytics about the community.
|
||||
* Set "SLAs" and accountability for maintainers or developers to have goals for their community engagement and at a system level makes sure things get done.
|
||||
|
||||
|
||||
|
||||
### Wrap up
|
||||
|
||||
Open source community managers need to apply these 5 levels of transparency to build a thriving open source community.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/2/transparency-open-source-communities
|
||||
|
||||
作者：[Emilio Galeano Gryciuk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[aREversez](https://github.com/aREversez)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/egaleano
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/OSDC_dandelion_520x292.png?itok=-xhFQvUj (Person in a field of dandelions)
|
||||
[2]: https://opensource.org/licenses
|
||||
[3]: https://opensource.com/tags/git
|
||||
@ -0,0 +1,111 @@
|
||||
[#]: subject: "5 levels of transparency for open source communities"
|
||||
[#]: via: "https://opensource.com/article/22/2/transparency-open-source-communities"
|
||||
[#]: author: "Emilio Galeano Gryciuk https://opensource.com/users/egaleano"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "aREversez"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
开源社区透明度的五个层次
|
||||
======
|
||||
如果想让开源社区繁荣发展，管理者需要达到透明度的五个层次。
|
||||
|
||||
![Person in a field of dandelions][1]
|
||||
|
||||
开源社区的管理者必须意识到社区有五个层次的透明度，这对于建设繁荣发展的开源社区来说至关重要。
|
||||
|
||||
本文将详细介绍各个层次及其目标与作用。不过首先，我想谈一谈透明度对开源社区的重要性。
|
||||
|
||||
### 为什么开源社区需要保证透明度？
|
||||
|
||||
* 透明能够增进社区成员之间的信任，促进合作。
|
||||
* 开放是社区合作和交流的前提。
|
||||
* 只有在开放透明的环境下，开源工作才能避免矛盾与冲突。
|
||||
* 社区管理者需要向参与者报告社区情况。
|
||||
* 向成员公开社区各项情况，营造信任氛围，有利于社区健康发展。
|
||||
|
||||
|
||||
|
||||
### 透明度的五个层次
|
||||
|
||||
#### 层次一：发布源码
|
||||
|
||||
在这一层次，社区需要遵循 [开放源码协议][2]，在 [Git][3] 等公开的版本控制系统上发布源码。
|
||||
|
||||
层次一的目标在于创建开源项目。
|
||||
|
||||
* 建立开源社区，理应达到这一层次。因为没有公开源代码，也就无所谓开源项目。
|
||||
* 开源项目的核心便是参与者们编写的源码，而源码需要获得开放源码协议批准的许可证。
|
||||
* 公开的版本控制系统能够促进合作，使得每一位开发者都能了解项目情况，理解合作模式。
|
||||
|
||||
|
||||
|
||||
#### 层次二：发布社区指南
|
||||
|
||||
达到这一层次，需要发布相关文档以及资源。也可通过组织活动，指导社区成员。
|
||||
|
||||
层次二的目标在于建立开源社区，促进社区发展。
|
||||
|
||||
* 建立一个活跃的社区需要的不仅仅是源代码。
|
||||
* 公开项目开展方式和贡献方式，能够吸引更多的开发者参与到项目当中。
|
||||
* 为了推动社区的发展，管理者可能需要举办一些重要活动，并为贡献者们筹办特殊活动。
|
||||
|
||||
|
||||
|
||||
#### 层次三：继往开来
|
||||
|
||||
到了这个层次，管理者有必要分享自己对于社区的见解，发布项目进展情况报告。
|
||||
|
||||
层次三的目标在于继往开来，确保社区进入后续阶段后能够更上一层楼，实现长远发展。
|
||||
|
||||
* 随着开源社区的发展，社区内的情况将会越来越难以把握。
|
||||
* 公开社区活动，让成员意识到自己的付出能够为公众所见，为公众所识。
|
||||
* 在这一层次，无论是报告还是分析，发布的时间并不固定，使用的工具也无定法。
|
||||
|
||||
|
||||
|
||||
#### 层次四：掌握社区的动态
|
||||
|
||||
这一层次就在于倾听社区声音：通过观察社区活动，关注项目发展；跟进软件开发进度，据此采取合适的应对措施。
|
||||
|
||||
层次四的目标在于保持科学严谨的态度，持续把握社区的发展情况及发展轨迹，引导社区朝着下一个层次迈进。
|
||||
|
||||
* 建立报告机制，运用分析工具，掌握社区动态。
|
||||
* 将社区的各项活动与社区成员的反响视作一种基准，用以比较社区内的其他活动。（译者注：由于译者能力有限，对原文本句所要表达内容的理解可能有误，故将原文附上以供参考：You can compare events in the community and the subsequent reactions of community members to a baseline and other events in the community.）
|
||||
* 坚持倾听社区声音，形成对于社区更深刻的见解。
|
||||
|
||||
|
||||
|
||||
#### 层次五：维护社区，长久发展
|
||||
|
||||
最后一个层次就是依据社区各项指标，提高社区成员的参与度。
|
||||
|
||||
层次五的目标在于制定行之有效、能够产生积极影响的决策方案，让开发者更好地参与社区项目。
|
||||
|
||||
* 适当调整系统，以适应社区各项指标的变动。
|
||||
* 跟进这些变动，理解它们是如何通过各项指标和数据分析体现出来的。
|
||||
* 针对社区维护者与开发者，制定服务等级协议和问责制度，为其设立参与度目标，确保项目整体顺利进行。
|
||||
|
||||
|
||||
|
||||
### 结尾
|
||||
|
||||
开源社区管理者需要做到上述五个层次，保证透明度，才能构建起一个繁荣发展的社区。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/2/transparency-open-source-communities
|
||||
|
||||
作者：[Emilio Galeano Gryciuk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[aREversez](https://github.com/aREversez)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/egaleano
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/OSDC_dandelion_520x292.png?itok=-xhFQvUj (Person in a field of dandelions)
|
||||
[2]: https://opensource.org/licenses
|
||||
[3]: https://opensource.com/tags/git
|
||||
Loading…
Reference in New Issue
Block a user