mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
Merge pull request #30573 from wxy/20220907-Open-source-events--4-goals-to-set-and-how-to-measure-them
ATRP:published/20220907 Open source events- 4 goals to set and how to measure them.md
This commit is contained in:
Xingyu.Wang
GitHub
commit
848a369275
@ -0,0 +1,95 @@
|
|||||||
|
[#]: subject: "Open source events: 4 goals to set and how to measure them"
|
||||||
|
[#]: via: "https://opensource.com/article/22/9/measure-success-your-open-source-event"
|
||||||
|
[#]: author: "Shaun McCance https://opensource.com/users/shaunm"
|
||||||
|
[#]: collector: "lkxed"
|
||||||
|
[#]: translator: "ChatGPT"
|
||||||
|
[#]: reviewer: "wxy"
|
||||||
|
[#]: publisher: "wxy"
|
||||||
|
[#]: url: "https://linux.cn/article-16434-1.html"
|
||||||
|
|
||||||
|
如何为举办开源活动设定目标并衡量它们
|
||||||
|
======
|
||||||
|
|
||||||
|
![][0]
|
||||||
|
|
||||||
|
> 通过定义目标并创建指标，衡量你的社区活动的成效。
|
||||||
|
|
||||||
|
活动是保持开源社区健康的重要组成部分。一个正面的活动体验可以激励当前的贡献者，并吸引新的参与者。但你如何判断自己的活动是否成功呢？
|
||||||
|
|
||||||
|
为了维护所涉及社区的健康，我们 CHAOSS （<ruby>社区健康分析开源软件<rt>Community Health Analytics Open Source Software</rt></ruby>）的 [应用生态系统工作组][2] 已经针对我们的活动考虑了这个问题。CHAOSS 应用生态系统包括一些针对 Linux 平台开发应用的项目。虽然现在主要由 GNOME 和 KDE 社区主导，但并不由它们定义。就当前而言，应用生态系统主要是由志愿者驱动的，他们是围绕自由软件的原则组织起来的。我们在此分享的工作是我们 2020 年 11 月 [针对开源活动的成功指标][3] 文章的更新。
|
||||||
|
|
||||||
|
我们遵循“目标-问题-指标”的方法论。首先，我们确定个人或组织可能设定的几个目标。然后，我们找出实现这些目标所需要回答的问题。最后，我们对每个问题设计可以提供答案的可量化指标。对于活动组织者，我们设定了四个目标。
|
||||||
|
|
||||||
|
### 目标 1：保留并吸引贡献者
|
||||||
|
|
||||||
|
贡献者是任何开源项目或生态的命脉，而活动则是贡献者体验中的核心。它们为吸引新贡献者提供了机会，同时也能够建立和巩固与现有贡献者的关系。活动应着眼于创造一个和谐而积极的氛围，以便与项目、生态和社区建立深远的关系。
|
||||||
|
|
||||||
|
我们需要考虑的一个问题是，参加活动的人在社区停留的时长是多久。如果活动的价值在于加强维持贡献者的关系，我们应当有办法去测量这个效果。要回答这个问题，需要对贡献和活动参与的长期数据进行分析。值得庆幸的是，许多项目已经拥有这些历史数据。
|
||||||
|
|
||||||
|
另一个问题是，活动参加者在我们的开源项目中扮演的是什么角色。活动通常都很专业化，可能并不能吸引那些想在 [非代码角色][4] 中贡献的人，如设计、文档编写和市场营销。如果项目能够跟踪非代码贡献，尽管这通常很有挑战性，你就可以对其与活动参与者名单进行对应。这些信息可以帮助活动组织者策划能吸引更广泛参与者群体的活动。
|
||||||
|
|
||||||
|
### 目标 2：举办有参与度的活动
|
||||||
|
|
||||||
|
活动不仅仅是演讲。它们为社区成员集结起来提供了空间。如果成员之间没有进行交流，那么这次活动就失去了其存在的价值。这也反映在所谓的走廊交谈中，即人们在走廊或会议日程安排之外进行的交流。一些会议甚至为那些没有打算参加任何环节，但希望在走廊里与他人交流的人减价售票。我们需要解决的问题是，如何衡量一个活动在推动参与者之间的交流上的成效。
|
||||||
|
|
||||||
|
要衡量会议时间的参与度，我们可以计算在问答环节中提出的问题数量。虽然这个指标直接受每个演讲者的影响，但活动组织者可以采取行动来鼓励问答环节的参与度。例如，活动组织者可以使用他们的早晨主题演讲来鼓励所有人通过提问来表示对演讲者的赞赏。
|
||||||
|
|
||||||
|
我们也考虑了在走廊交谈中的参与情况。一种衡量方法是观察人们在非会议时间的行为。另一种方法是在活动结束后的调查中询问参与者的非会议时间的体验。
|
||||||
|
|
||||||
|
最后，我们考虑了在虚拟空间的参与情况。一种衡量方法是通过计算在社交媒体上使用活动标签或者来源于我们知道正在参加活动的人发出的信息数量。另一种可能性，无论在线还是现场，都可以设置一种表情符，参与者只需单击即可反映对会议环节、主题演讲和整个会议体验的反应。
|
||||||
|
|
||||||
|
### 目标 3：深入了解公司的贡献
|
||||||
|
|
||||||
|
企业和其他机构对活动，甚至社区活动的贡献是极其重要的。他们可能提供赞助、派遣员工去帮助组织，或者只是派员工去参加活动。确保公司在他们的贡献中找到价值是很重要的，但我们必须以不排斥社区贡献的方式来做这件事。我们研究了公司对社区活动的期望，以及我们可以通过何种方式的衡量来提高公司的贡献。
|
||||||
|
|
||||||
|
有些开源活动被认为比其他活动更具有公司味，所以你可能会问，有多少比例的参与者是被他们的雇主派遣去参加的，而不是作为志愿者参加的。有时，这种差异体现在门票定价上。否则，这是一个可以在注册调查中轻松问到的问题。虽然这些信息很有用，但这并不是一个完美的指标，因为付费的开源贡献者通常会在他们的工作职责之外参加活动。
|
||||||
|
|
||||||
|
我们还考虑了几个指标，比如哪些公司参加活动，除了派遣员工（例如，金钱赞助活动），公司在做什么，以及公司是否会重复参与。认识到这一点对培养长期关系很重要。
|
||||||
|
|
||||||
|
最后，我们考虑了具有相似范畴的活动的竞争格局。公司在活动上的预算有限。尽管我们喜欢类似的活动，但他们都从同一池子里的潜在赞助商中吸引人。了解哪些其他活动正在寻求赞助可以帮助组织者更好地区分他们自己的活动。
|
||||||
|
|
||||||
|
### 目标 4：关注多元化和技能差距
|
||||||
|
|
||||||
|
由全球各地的人们构建和发展起来的国际社区，这些人来自多种多样的背景，是开源项目的一个重要组成部分。这些社区贡献他们的想法，为共同的目标合作，帮助项目扩大和开拓新的方向。
|
||||||
|
|
||||||
|
面对面活动对于项目和组织来说是一个独特的机会，可以让他们的贡献者聚集在一起，让他们交流并分享各种多元的经验，进而推动创新，以不同的视角促进增长。这也是一个培养和强化共享文化的机会，重点在于增加多元化和包容性。这些指标应该能衡量活动对于培养这种多元性，以及在社区中填补技能缺口的贡献有多大。
|
||||||
|
|
||||||
|
我们首先考虑我们在活动中有哪些技能培训，以及这些培训包含多广泛的技能。技能培训可以包括教程，动手实践的工作坊，黑客马拉松，或者其他很多形式。我们在编码之外的技能上有技能培训吗？有很多对开源项目有价值的技能和角色，比如组织活动所需要的技能。
|
||||||
|
|
||||||
|
然后，有助于看看我们在我们的社区内需要哪些技能，而哪些技能又是缺失的。项目领导和参与培训的人通常是获取此类信息的良好来源。通过将我们拥有的技能培训与社区需要的技能进行比较，我们可以更好地设计未来活动的培训项目。
|
||||||
|
|
||||||
|
### 参与其中
|
||||||
|
|
||||||
|
CHAOSS 应用生态系统工作组对与活动组织者共同细化并实施指标表示感兴趣。KDE 和 GNOME 活动的组织者已经讨论了怎样改变他们的活动以更好地捕捉到这些指标。我们为活动组织者的工作也 [以 PDF 形式提供][7]。
|
||||||
|
|
||||||
|
CHAOSS 应用生态系统工作组还挑战了定义开源软件应用生态系统内的市场营销和通信功能指标。朝向这个目标的第一步是和 KDE 和 GNOME 扮演这个角色的人们进行的一次对话。这次对话可以在 [CHAOSScast Episode #31: Marketing Metrics for OSS Foundations and Projects][8] 中找到。我们将从这次对话中得到的学习经验转化为目标-问题-指标，如上述对活动组织者指标的描述。
|
||||||
|
|
||||||
|
在我们对推广和通信团队的工作之后，我们计划解决财务团队、社区经理、发布经理、跨项目协调人和导师的指标。我们的工作才刚刚开始，我们欢迎反馈和新的贡献者。
|
||||||
|
|
||||||
|
你被邀请参与 CHAOSS 应用生态系统工作组的工作。你可以在我们的 [GitHub 页面][9] 上找到更多的信息。
|
||||||
|
|
||||||
|
*（题图：MJ/187d7b91-9f02-47a2-a433-ea5adbbe1ac6）*
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/22/9/measure-success-your-open-source-event
|
||||||
|
|
||||||
|
作者：[Shaun McCance][a]
|
||||||
|
选题：[lkxed][b]
|
||||||
|
译者：[ChatGPT](https://linux.cn/lctt/ChatGPT)
|
||||||
|
校对：[wxy](https://github.com/wxy)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://opensource.com/users/shaunm
|
||||||
|
[b]: https://github.com/lkxed
|
||||||
|
[1]: https://opensource.com/sites/default/files/lead-images/team_global_people_gis_location.png
|
||||||
|
[2]: https://github.com/chaoss/wg-app-ecosystem
|
||||||
|
[3]: https://opensource.com/article/20/11/chaoss-open-source-events
|
||||||
|
[4]: https://opensource.com/article/22/8/non-code-contribution-powers-open-source
|
||||||
|
[5]: https://opensource.com/article/22/6/attract-contributors-open-source-project
|
||||||
|
[6]: https://opensource.com/article/19/4/ways-support-sustain-open-source
|
||||||
|
[7]: https://github.com/chaoss/wg-app-ecosystem/blob/main/Metrics%20for%20OSS%20Event%20Organizers%20-%20CHAOSS%20App%20Ecosystem%20(Oct%202021).pdf
|
||||||
|
[8]: https://podcast.chaoss.community/31
|
||||||
|
[9]: https://github.com/chaoss/wg-app-ecosystem
|
||||||
|
[0]: https://img.linux.net.cn/data/attachment/album/202312/02/120138aq5dddcsdsnnf8n8.png
|
||||||
@ -1,91 +0,0 @@
|
|||||||
[#]: subject: "Open source events: 4 goals to set and how to measure them"
|
|
||||||
[#]: via: "https://opensource.com/article/22/9/measure-success-your-open-source-event"
|
|
||||||
[#]: author: "Shaun McCance https://opensource.com/users/shaunm"
|
|
||||||
[#]: collector: "lkxed"
|
|
||||||
[#]: translator: " "
|
|
||||||
[#]: reviewer: " "
|
|
||||||
[#]: publisher: " "
|
|
||||||
[#]: url: " "
|
|
||||||
|
|
||||||
Open source events: 4 goals to set and how to measure them
|
|
||||||
======
|
|
||||||
Measure the success of your community events by defining goals and creating metrics.
|
|
||||||
|
|
||||||
![Team of people around the world][1]
|
|
||||||
|
|
||||||
Events are an essential component of open source community health. A positive event experience can inspire current contributors and encourage new ones. But how can you tell whether your events are successful?
|
|
||||||
|
|
||||||
We at the [CHAOSS (Community Health Analytics Open Source Software) App Ecosystem Working Group][2] have considered this question for our events to maintain the health of the communities involved. The CHAOSS App Ecosystem includes several projects focused on developing applications for the Linux platform. While currently dominated by the GNOME and KDE communities, it is not defined by them. The app ecosystem, as it stands today, is primarily driven by volunteers with altruistic goals organized around free software principles. The work we share in this article is an update from our November 2020 article about [success metrics for open source events][3].
|
|
||||||
|
|
||||||
We follow the goal-question-metric approach. We first identify several goals that a person or organization might have. We then identify questions we need to answer to achieve those goals. Finally, for each question, we consider quantifiable metrics that provide answers. For event organizers, we established four goals.
|
|
||||||
|
|
||||||
### Goal 1: Retain and attract contributors
|
|
||||||
|
|
||||||
Contributors are the lifeblood of any open source project or ecosystem, and events are a core part of the contributor experience. They are an opportunity to attract new contributors, and they can build and reaffirm relationships that help retain existing contributors. Events should be geared toward creating a harmonious and enthusiastic atmosphere that builds relationships with the project, ecosystem, and community.
|
|
||||||
|
|
||||||
One question to consider, then, is how long people who attend events stay with the community. If the value of events is to strengthen the relationships that retain contributors, we should be able to measure that. Answering this question requires long-term data on contributions and event attendance. Fortunately, many projects will already have this historical data.
|
|
||||||
|
|
||||||
Another question is what roles event attendees have in our open source projects. Events can often be highly technical and may not attract people who want to contribute in [non-coding roles][4], such as design, documentation, and marketing. If projects have the means to track non-code contributions, which is often tricky, you can correlate with event attendee lists. This information can help event organizers create events that attract a wider audience.
|
|
||||||
|
|
||||||
### Goal 2: Have engaging events
|
|
||||||
|
|
||||||
Events are more than presentations. They create a space for community members to come together. If they don't engage with each other, the event is a lost opportunity. The importance of interactions between members is also evident in the so-called hallway track, the name given to engagement that occurs in the hallways and outside the regular event schedule. Some conferences even have discounted tickets for people who don't plan to attend any sessions but want to engage with others in the hallway track. The question for us is how to measure an event's success in terms of how it fosters engagements between event participants.
|
|
||||||
|
|
||||||
To measure engagement during regularly scheduled sessions, we could count the number of questions asked during a Q&A session. While the individual speakers directly influence this metric, there are things event organizers can do to encourage Q&A participation. For example, event organizers can use their morning keynote to encourage everyone to ask questions as a form of showing appreciation.
|
|
||||||
|
|
||||||
We also considered engagement during the hallway track. One way to measure this is observing how people behave when not in sessions. Another way to measure this is to ask participants in a post-event survey about their experience outside of scheduled sessions.
|
|
||||||
|
|
||||||
Finally, we considered engagement in virtual spaces. One option for measuring this is through the number of social media messages that use the event's hashtag or from people we know are at the event. Another possibility for online or even in-person sessions is to have an emoji that could be collected as an easy one-click reaction to sessions, keynotes, and general conference experience.
|
|
||||||
|
|
||||||
### Goal 3: Understand company contributions
|
|
||||||
|
|
||||||
Companies and other organizations are essential contributors to events, even community events. They may provide sponsorship, sponsor employees to help organize, or simply send employees to the event. It's important to ensure companies find value in their contributions, but we must do this in a way that doesn't alienate community contributions. We looked at what companies expect from community events and what we can measure to improve company contributions.
|
|
||||||
|
|
||||||
Some open source events have a reputation for being more corporate than others, so one question you might ask is what percentage of attendees are sent by their employer rather than attending as volunteers. Sometimes, the difference is built into ticket pricing. Otherwise, it's an easy question to ask on a registration survey. Although this information is helpful, it is an imperfect metric because paid open source contributors often attend events outside their job responsibilities.
|
|
||||||
|
|
||||||
We also considered several metrics around which companies are attending events, what companies are doing apart from sending employees (for example, financially sponsoring the event), and whether companies repeat their involvement. It's important to recognize this to cultivate long-term relationships.
|
|
||||||
|
|
||||||
Finally, we considered how competitive the landscape of similarly scoped events is. Companies only have so much budget to spend on events. As much as we enjoy similar events, they draw from the same pool of potential sponsors. Understanding which other events are seeking sponsorship can help organizers better differentiate their own events.
|
|
||||||
|
|
||||||
### Goal 4: Address diversity and skill gaps
|
|
||||||
|
|
||||||
The international communities built and developed across the globe, consisting of people from diverse backgrounds, are an essential component of open source projects. These communities contribute their ideas, collaborate on common goals, and help the project expand and scale toward new directions.
|
|
||||||
|
|
||||||
In-person events are a unique chance for projects and organizations to bring their contributors together and allow them to interact and exchange diverse experiences, boosting innovation and accelerating growth from different perspectives. They are also an opportunity to cultivate and reinforce a common culture, focusing on increasing diversity and inclusion. These metrics should measure how well an event contributes to fostering this diversity and closing skill gaps in the community.
|
|
||||||
|
|
||||||
We started by considering which skill programs we have at our events and how wide a breadth of skills these programs represent. Skill programs could include tutorials, hands-on workshops, hackathons, or many other formats. Do we have skill programs around skills other than coding? There are many skills and roles valuable to open source projects, such as the skills required to organize events.
|
|
||||||
|
|
||||||
It's then helpful to look at which skills we need in our community and which skills are lacking. Project leads and people involved in onboarding are often a good source of this information. By comparing the skills programs we have with the skills our community needs, we can better design the programs for future events.
|
|
||||||
|
|
||||||
### Get involved
|
|
||||||
|
|
||||||
The CHAOSS App Ecosystem working group is interested in working with event organizers to continually refine and implement metrics. The KDE and GNOME event organizers have already discussed changing their events to better capture some of these metrics. Our work for event organizers is also [available as a PDF][7].
|
|
||||||
|
|
||||||
The CHAOSS App Ecosystem working group is also taking up the challenge of defining metrics for the marketing and communications functions within OSS App Ecosystems. The first step towards this goal was a conversation with folks from KDE and GNOME fulfilling this role. The conversation is available as [CHAOSScast Episode #31: Marketing Metrics for OSS Foundations and Projects][8]. The learnings from this conversation are next translated into goals-questions-metrics, as described above for the event organizer metrics.
|
|
||||||
|
|
||||||
After our work on promotions and communications teams, we plan to address metrics for finance teams, community managers, release managers, cross-project coordinators, and mentors. Our work has only begun, and we welcome feedback and new contributors.
|
|
||||||
|
|
||||||
You are invited to join the work of the CHAOSS App Ecosystem WG. Find more information on our [GitHub page][9].
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://opensource.com/article/22/9/measure-success-your-open-source-event
|
|
||||||
|
|
||||||
作者：[Shaun McCance][a]
|
|
||||||
选题：[lkxed][b]
|
|
||||||
译者：[译者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/shaunm
|
|
||||||
[b]: https://github.com/lkxed
|
|
||||||
[1]: https://opensource.com/sites/default/files/lead-images/team_global_people_gis_location.png
|
|
||||||
[2]: https://github.com/chaoss/wg-app-ecosystem
|
|
||||||
[3]: https://opensource.com/article/20/11/chaoss-open-source-events
|
|
||||||
[4]: https://opensource.com/article/22/8/non-code-contribution-powers-open-source
|
|
||||||
[5]: https://opensource.com/article/22/6/attract-contributors-open-source-project
|
|
||||||
[6]: https://opensource.com/article/19/4/ways-support-sustain-open-source
|
|
||||||
[7]: https://github.com/chaoss/wg-app-ecosystem/blob/main/Metrics%20for%20OSS%20Event%20Organizers%20-%20CHAOSS%20App%20Ecosystem%20(Oct%202021).pdf
|
|
||||||
[8]: https://podcast.chaoss.community/31
|
|
||||||
[9]: https://github.com/chaoss/wg-app-ecosystem
|
|
||||||
Loading…
Reference in New Issue
Block a user