document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2024-12-26 21:30:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

ATRP

Browse Source 
@wxy
https://linux.cn/article-16179-1.html
This commit is contained in:
Xingyu Wang 2023-09-11 09:20:25 +08:00
parent 16e1635068
commit 534da7f9ca
2 changed files with 297 additions and 305 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

305
sources/talk/20230213.1 ⭐️⭐️⭐️ A 10-step guide for a successful hackathon.md
View File

@ -1,305 +0,0 @@
[#]: subject: "A 10-step guide for a successful hackathon"
[#]: via: "https://opensource.com/article/23/2/hackathon-guide"
[#]: author: "Tiffany Long https://opensource.com/users/tiffany-long"
[#]: collector: "lkxed"
[#]: translator: " "
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
A 10-step guide for a successful hackathon
======
Hackathons are easy. How much thought do you need to put into them anyway? Just set a date, and people will show up. Well, that is not quite true!
While you may get lucky with that approach, the reality is that hackathons are a keystone experience in the tech industry, and attendees have specific expectations. Not only that, but your organization also has certain needs and should set goals for a hackathon. So, how do you ensure that a hackathon works for your organization and attendees?
A successful hackathon depends on several decisions that tend to be recursive. Decisions about what you want to achieve will impact what resources you allot and how you want to communicate. Those decisions affect whether you go virtual or in person, and that decision will once again impact the resources you need and how you communicate. Alignment when planning hackathons is not just about getting people to agree. You will have a whole suite of decisions that must internally align. For example, a technically difficult hackathon might not be able to attract a large audience (ask me how I know!) and will require a specialized recruitment strategy that requires different resources.
I've done many hackathons over the years, including just a few months back, when my organization hosted a hackathon that led to new features that we will incorporate into the next version of our open source product, Traefik Proxy 3.0. So, trust me when I say planning a hackathon that will enrich attendees and create valuable outcomes for your project is about more than hope, pizza, and chaos.
This article uses the most recent Traefik Labs Hackathon as a blueprint. I share a checklist, tips, and tricks to help you identify your objectives, plan, manage the contest and compensation, share your results, and manage the long tail of the hackathon (the work isn't over when the hackathon ends!)
This guide serves as a model for you to outline best practices so that you, too, can hold a successful hackathon with a sizable target audience that delivers results!
- [Three questions to determine your goals][1]
- [Why are you doing this?][2]
- [Who is your audience?][3]
- [How are you measuring goals?][4]
- [Decide on in-person vs. virtual][5]
- [Build your communication strategy][6]
- [Decide on the prizes][7]
- [Swag it up][8]
- [Get the word out][9]
- [Managing the long tail][10]
**[ Get a PDF and EPUB version of this article. [Download it here.][11] ]**
### 1. Three questions to determine your goals
The first and most crucial step is to set your goals. But this is no simple affair. Before you set goals, you need to coordinate internally on multiple fronts and ask questions such as:
- Why do you want to do a hackathon?
- Who do you want to attend?
- How are you going to measure your success?
#### Identify your internal stakeholders and set expectations
**Hackathons are cross-functional**. No hackathon is run by a community person alone. It is important to ensure everyone is aligned on the goals, what is required to achieve them, and that the necessary resources are committed. This probably sounds super corporate, but these functions exist even within the smallest projects. A project needs adoption and code. It also needs value decisions based on who will be using it. And, of course, projects need passionate contributors.
**Hackathons require cross-functional resources**. One team with a single set of resources cannot successfully run a hackathon. The organization must make various resources available, including:
- Marketing for planning and outreach.
- Product Management for product and industry-specific insight.
- Engineering for deep technical knowledge and community engagement.
For these reasons, hackathons usually support cross-functional goals. Your Community Team, for example, might want to build ownership and convert users to active community members. The Marketing Team might want to enhance awareness and court new users. The Engineering Team might need new perspectives on specific needs or challenges. The Product Team might have goals or no-go areas the community should be aware of.
And last but not least, the hackathon budget is cross-functional. I am sorry to inform you, but hackathons ain't free! Your largest expense is always the dedicated time of your team.
### 2. Why are you doing this?
Setting your goals is the most important part of a successful hackathon. If you don't know what you want to do or why a hackathon is important, at best, it will have a ton of wasted potential and be a disconnected mess at worst.
Communities feed off of ownership. Decide what you need from your community and what ownership stake you want community members to have. Without a clear understanding of this, your hackathon might not reach its full potential in empowering your community.
Be very careful with your hackathon design and goals. Different types of hackathons appeal to different skill levels. If the code you're looking for is very advanced, take the extra time to court the right audience and accept that it will include less overall attendance. Cast a wide net if the contributions can vary in skill and experience.
#### Are you hosting a hackathon to get code and build your project?
- Sometimes, projects hit a critical juncture or acquire a lot of excitement around them, and you want to harness the energy to build something together. A hackathon is a great way to achieve this!
- If you have an active community of users, a hackathon can bring everyone together at the same time to harness that excitement to feed the creative energy of your group.
**Note:** This is more easily achievable with smaller groups who know each other and have a shared experience with the project. You also need to carefully evaluate the skills required to build your project.
#### Are you hosting a hackathon to build your community or re-engage them?
- Maybe you are just building your community or noticed that your community needs a little juice. Hackathons are exciting, and they can help bring that back.
- Above, I said, "Communities feed off of ownership." If your community members do not feel they have a stake or that their needs and voices matter, they will drift away. This is common when projects grow and become more formalized. As the barrier to entry rises, the ability for community members to feel ownership falls, and the project becomes like a product to the user. One way to enhance community membership is by creating events that engage users and lower the bar for entry: Bug round-ups, light requests, and longer timelines.
- Perhaps your user community is growing, but the contributor community is becoming more specialized as your tech becomes more complex. In this case, you need to court sophisticated technologists who understand your tech and the use cases. Look for community members who use your tech in their jobs—especially at companies with large or complex deployments. These people are more likely to understand the needs of users and of the tech itself. They will also have suggestions for significant and valuable enhancements.
- You are free to choose goals that build your community and match your team and community members' energy and time. For example, at Traefik Labs, a hackathon aimed at enthusiastic folks with a small time commitment might target our Plugin Catalog. However, when looking for larger contributions or contributions that take significant expertise, we might target advanced technologists–especially those we know.
#### Are you hosting a hackathon to celebrate something?
- Hackathons are a great way to celebrate a new launch and hype your community. For example, that is exactly why we hosted the [Traefik Proxy 3.0 Hackaethon][12].
- Hackathons are also great for getting the word out about a new product capability. The [Traefik Plugin Hackaethon][13] is an excellent example here.
- Maybe you want to organize an event to celebrate your top contributors. Do it with a hackathon! Take a look at [this hackathon organized by HackerOne][14]. And if you're thinking, "but this is not about open source software (OSS), how can it be a hackathon?" I've got news for you—hackathons are not just for OSS! Hackathons are for creating with a large community.
#### Are you hosting a hackathon to build awareness?
Hackathons are a great place to begin if you are just starting and want to build awareness around your product/brand. However, there are a few conditions.
- Laser-focused goals and big contributions are unlikely to happen at this stage. Go for a softer, broader focus, and minimize the work required by attendees.
- Reach out to new community members, less experienced users, and users with less exposure to your specific project.
#### Are you hosting a hackathon to connect to users?
I can think of no better way to connect new users to your project than a hackathon. Not only will your users become intimately familiar with your project, but hackathons also have a unique way of engendering a sense of ownership, rarely achievable through other types of events.
### 3. Who is your audience?
Assuming you have pinpointed why you want to host a hackathon and what you want to achieve, it's time to assess the characteristics that a participant needs to be successful. Use your decisions about your goals to identify your audience to ask what type of community member can help you achieve your objectives. Use the list of comparisons below:
- Highly-skilled vs. mixed-skilled vs. low-skilled
- Specialized vs. generalized skill
- Intensive time vs. less intensive time
- Individual contributions vs. group contributions
Your most active community members must look a bit like your target audience.
You might rethink your goals if your target audience doesn't align with at least 80% of the people you know you can attract. Accurately identifying your target audience will go a long way to making your communication strategy around the hackathon and the hackathon itself more successful.
### 4. How are you measuring goals?
Perfect, now that you answered the first two big questions and have your goals laid down, it's time for the third big question—how will you measure those goals? Inspiring your internal teams and your community to work together in building the future of your project, engendering ownership, and increasing engagement are awesome, but you can't determine success if you can't measure your goals.
#### What does success look like immediately after the event?
- A major sign of success is whether attendees connect and engage with each other, co-educate, and build teams during their hackathon.
- Were mentorships built? Through partnership, did several newer users grow into skilled mid-level users, or did mid-level users evolve into expert-tier users? This is the gold ring of success indicators.
- Did your partner organizations (maybe universities) request future hackathons or other events?
- Clearly, the first sign of success is that your attendees had an overall good experience and are motivated to engage more with your project.
- If you are looking for outreach, set a quantity of participants to shoot for and a number of participants who return to contribute more after the event or in three months.
- If building awareness, you might also look for successful follow-up chatter. Who wrote blog posts? Were attendees talking about it on social media?
- If you are looking for contributions, did they work for you? Are these the contributions you want? Did they impact how your team thinks about the problems they face? Will you have ongoing collaborations with these contributors?
#### What will denote success three months after the event?
Defining benchmarks for long-term success is just as important. Here are a few examples of what could indicate long-term success:
- Your hackathon should increase the number of returning contributors to your project. The goal is to get people hooked. If people new to your project came from the hackathon and stayed as users, or if your existing users became more active, you know you won.
- Hackathons are great as self-contained events, but they are supremely valuable as marketing content. They build trust in the community, showing you are responsive and value community input. They are fun loci of activity that let community members bond and look forward to the future, and they are aspirational. People love to see others celebrated and plan to achieve that celebration in the future.
- When you build marketing content around your hackathon (or better yet, others build content around your hackathon), you can expand your reach among second-degree connections.
- Tall poppy syndrome is a shame. Hackathons are a great opportunity to gather those participants who stood out and galvanize them to do other cool things and spread the word about your project.
### 5. Decide on in-person vs. virtual
I know what you're thinking—is in-person even a consideration? We've all gotten so used to doing everything virtually in the post-covid world. So, are the days of in-person gone? I would argue no, they are not. With care and safety measures in place, in-person events are the heart and soul of hackathons.
- In-person means no distractions, lots of pizza, and energy drink-fueled friendship.
- In-person fuels group participation rather than individual contributor participation.
- In-person works well at scale and in miniature: Organizing in-person hackathons for large groups brings high energy and rewards. But they can get quite costly. If you want to organize a large-scale hackathon, you'll be more successful if you target less experienced developers (students, clubs, new careerists) because these folks have the most time and the most to gain when demonstrating their skill and passion.
- In-person also works well for small groups and is great for intense planning and iteration—long nights with new and old friends, usually over food and beer!
And while many pros come with in-person hackathons, it doesn't mean that the virtual experience only comes with cons. Granted, nothing replaces that feeling of late nights with pizza, off-the-cuff remarks that end up changing your entire project, and a friendly set of eyes over your shoulder as you test or debug. But...
- Virtual means you can get a wider group of participants at a significantly lower cost.
- Virtual respects disability.
- Virtual is geolocation friendly.
- Virtual allows for higher individual contributor participation.
- Virtual offers more flexibility in the style and length of the event – you cannot have a month-long in-person event!
#### Timelines of virtual hackathons
Did you decide to do a virtual hackathon? Great! Now, you need to determine the type of virtual hackathon you want. Do you envision a prolonged or intensive timeline? Keep in mind that the type of [virtual hackathon][15] you choose will determine, to some extent, your target audience and communication strategy.
**Extended timeline:**
- Allows after-hours tinkering and enables developers to attend without taking time off from work.
- Provides more time to solicit contributions.
- Requires fewer resources for both the organizer and the participants.
- Extended timelines require fewer real-time resources.
**Intense timeline:**
- Recreates that feeling of intensity usually experienced in in-person hackathons.
- Requires a high amount of resources for a short period of time.
- Requires tight management and a communication platform.
- Requires clear one-on-one communication, but also fosters group-to-group or intra-community communication.
### 6. Build your communication strategy
Speaking of communication, once you have your goals, you must decide **who** communicates with participants and **how**. It's common to choose between the popular apps of the day. Your choice impacts the event's feel. Different [chat applications][16] and [collaboration platforms][17] have their own cultures and strengths. The decision you made early on about how to host your hackathon (in-person or virtual, prolonged or intense timeline) is likely to have the most significant impact on your communication strategy.
#### In-person communication plan
If you are running an in-person hackathon, consider it a genuine event—it feels almost like a conference. In-person hackathons often include the following:
- **Workshops/round tables:** Meant to educate and develop new industry standards/best practices for the concerns of the day. These sessions can function as proctored time-bound conversations amongst 6-10 individuals, where they agree upon findings and take notes that are made public to all participants.
- **Planning sessions:** Often used for projects with non-code outcomes, like developing updated standards.
- **Coding sessions:** Used for code-based projects which require work to maintain and enhance.
Each of the above has different communication needs:
- People prepared to facilitate, but not lead, conversations in workshops.
- Note takers and people to make sure that the notes are turned into a publishable product.
- Project managers to ensure the above tasks are done.
- General communication for running the event (food, cleaning, management of resources).
- Masters of ceremonies to move through the agendas.
- For workshops:
Making this all happen requires the resources and specialized knowledge from your Community, Product Managers, and teach-savvy teams. From past experience, it took a team of community members and staff to manage an event of this scope. To be successful, your team will need specialized people as well.
You also need to decide what types of communication you want to foster and who is responsible for it:
- Multiple teams will need to take shifts to perform general support.
- A DevRel, engineering, or support team will need to manage technical communication between triage and participants.
- Community Teams usually spend extensive time connecting participants to help build strong groups by reinforcing skills or points of view. This is one way to ensure that hackathon magic.
- Community Teams also need to support marketing efforts to engage participants and manage follow-up.
#### Virtual communication plan
For virtual hackathons, the choice of a communication platform depends heavily on the outcome you want to achieve, the timeline you've chosen for your hackathon (prolonged or intensive), and the type of communication you wish to facilitate (synchronous or asynchronous).
**Using Pull Requests and Issues on Git hosts (asynchronous):**
- Choosing to communicate through Git pull requests and Issues on your project directly frees up technical staff resources because it keeps the conversations about projects in your current process and allows your team to be responsive rather than instigating communication.
- This approach is great if the team for your hackathon is small or if the expected contributions are relatively small and you do not plan to help participants form teams.
- Using your existing processes is especially great for prolonged hackathons as they do not require additional moderation or require your team to monitor an additional app.
- The downside is that you will only facilitate communication with the individual contributor or group of contributors already working together. It's difficult to connect participants who are working separately. Participants can't find each other as easily on their own, so you lose some of the magic that happens when hackathon participants organically talk to each other in open threads.
**Using a chat application (synchronous):**
- Choosing dedicated chat servers is required for intense hackathons.
- Chat facilitates the team formation and communication necessary for complex projects with fast timelines and sparks the brainstorming that preludes an awesome contribution.
- Additionally, your goal is to build community. People want to join communities where they have ownership, have friends, and feel comfortable. You need a place for participants to feel connected to each other if you want them to return.
- Chat servers can outlast an event, allowing for continued community engagement.
Regardless of which platform you choose, you need a communication plan that identifies when every person on your team is available. Managing a virtual hackathon can get quite tricky, primarily due to the different timezones—people can participate whenever they want, from wherever they want. You must plan to accommodate participants across all time zones and for every occasion. Draw up a plan with who is responsible (and when) for the following:
- Determining response SLAs.
- Animating your virtual space (a dead space guarantees poor communication).
- Encouraging team building.
- Responding to technical questions.
- Checking in on participants.
- Moderating the space to ensure the safety of your participants.
### 7. Decide on the prizes
Is your hackathon a contest? Hackathon participants are often content with grand prizes and "swagpaloozas" for top contributions. But before you decide on the fun stuff (the actual awards), you must determine what your contest values.
- What differentiates a good contribution from a great contribution? If your attendees know how you feel about this, they are more likely to hit it out of the park.
- What do you value? This is your chance to tell participants what you want to see submitted by attaching a prize to it. For example, during the last Traefik Hackaethon, we offered bounties for the most-wanted features. These were, indeed, the ones most people worked on.
- Are there categories of contributions? You need to decide on prizes for each category.
- Create a rubric (a chart or grid defining and ranking achievements, [like this example][18]). This way, participants know what you value and how they are judged. This was one way we improved submissions at HackerOne.
On the other hand, some may argue that competition is overrated. If your goal is participation, feel free to reward every single one of your participants for simply giving back! [Hacktoberfest][19] is a great example of this approach.
### 8. Swag it up
Everyone loves swag! And your participants would certainly appreciate a token to remember this event, whether virtual or in person. Swag has two purposes:
- Swag shows your appreciation: The contributors took their time to engage with you in an intense way; thank them with a gift that shows you value their contributions.
- Swag builds awareness: Gifting swag to your participants helps them spread the love and build awareness of your community by sharing their loot and experience.
The community loves swag, but they don't love boring swag! You probably distributed your existing t-shirts and stickers during another event. Make your hackathon memorable and go for new, exciting, and exclusive designs. Shirts are great, and hoodies reign supreme. But think about cool swag participants may not have already. Think of something that could become their new staple item, like backup batteries or hats (both popular at HackerOne). Personally, my own home features some towels and slippers from hackathons!
### 9. Get the word out
Setting your goals and deciding on amazing grand prizes and swag are all important steps. But how will anyone know your hackathon is happening if you don't get the word out? You need to investigate the available channels carefully, and you need to be bold with your promotion. I'm talking blogs, vlogs, emails, social media—anything you can get your hands on.
However, depending on your defined goals, you need to invest in the appropriate channel. Where you advertise depends on who you want to invite to your hackathon.
- IIf you want to attract more experienced users, target big organizations where your project is used. LinkedIn and email promotion would be most effective here.
- If you want to bring in new and less experienced users, you're better off targeting universities and boot camps. Promoting the event on community-based media, like Mastodon, Matrix, Mattermost, Reddit, Discourse, Discord, and any place your target audience hangs out is a better choice.
### 10. Managing the long tail
Yay, the hackathon is over! Now all hackathon-related activities can stop, and we no longer need to pull resources, right? Wrong! Think of hackathons as only one step of the road in a series of events in your software development and community building. To deem your hackathon a success, you must be prepared to engage in post-event activities.
- Communicating your results: Don't forget to communicate hackathon outcomes internally and externally. Demonstrate the ownership the community members gained during the hackathon to grow trust in your community and project.
- Building community: Lean on your hackathon participants for future community activity.
- Putting together the retrospective: What went well, what went terrible, what was meh, what surprised you? This analysis is how you grow, change, and iterate. Don't forget to do a blameless retro as soon as possible so it is all fresh in your mind.
### Wrap up
If you started reading this article thinking that hackathons aren't that hard to pull off, I'm sorry to have burst your bubble! And although I sincerely believe hackathons are a great way to engage and communicate with your community on so many levels, having just the intention does not guarantee the results.
For a hackathon to be successful, you need to be meticulous and prepared to invest significant resources and effort to plan and execute it properly.
Thank you for reading, and I hope this checklist helps you successfully organize your next hackathon!
--------------------------------------------------------------------------------
via: https://opensource.com/article/23/2/hackathon-guide
作者：[Tiffany Long][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/tiffany-long
[b]: https://github.com/lkxed/
[1]: https://opensource.com/article/23/2/hackathon-guide#set-your-goals
[2]: https://opensource.com/article/23/2/hackathon-guide#why-are-you-doing-this
[3]: https://opensource.com/article/23/2/hackathon-guide#who-is-your-audience
[4]: https://opensource.com/article/23/2/hackathon-guide#how-are-you-measuring-goals
[5]: https://opensource.com/article/23/2/hackathon-guide#decide-on-in-person-vs-virtual
[6]: https://opensource.com/article/23/2/hackathon-guide#build-your-communication-strategy
[7]: https://opensource.com/article/23/2/hackathon-guide#decide-on-the-prizes
[8]: https://opensource.com/article/23/2/hackathon-guide#swag-it-up
[9]: https://opensource.com/article/23/2/hackathon-guide#get-the-word-out
[10]: https://opensource.com/article/23/2/hackathon-guide#managing-the-long-tail
[11]: https://opensource.com/downloads/hackathon-guide
[12]: https://traefik.io/blog/announcing-traefik-proxy-3-0-hackaethon/
[13]: https://traefik.io/blog/announcing-the-inaugural-traefik-hackaethon-2020-in-october/
[14]: https://www.youtube.com/watch?v=9VZCD9TirCg&list=PLxhvVyxYRvibM_KJBPtPsfEcjnP5oGS8H
[15]: https://opensource.com/article/20/8/virtual-hackathon
[16]: https://opensource.com/alternatives/slack
[17]: https://opensource.com/article/21/9/alternatives-zoom
[18]: https://www.isothermal.edu/about/assessment/assets/rubric-present.pdf
[19]: https://hacktoberfest.com/

297
translated/talk/20230213.1 ⭐️⭐️⭐️ A 10-step guide for a successful hackathon.md Normal file
View File

@ -0,0 +1,297 @@
[#]: subject: "A 10-step guide for a successful hackathon"
[#]: via: "https://opensource.com/article/23/2/hackathon-guide"
[#]: author: "Tiffany Long https://opensource.com/users/tiffany-long"
[#]: collector: "lkxed"
[#]: translator: "ChatGPT"
[#]: reviewer: "wxy"
[#]: publisher: "wxy"
[#]: url: "https://linux.cn/article-16179-1.html"
成功举办黑客马拉松的 10 步指南
======
![][0]
> 想要规划、主办及管理一次成功的黑客马拉松，请遵循以下蓝图。
初看起来，<ruby>黑客马拉松<rt>hackathon</rt></ruby>是很简单的事情。你需要为它投入多少准备呢？仅设置一个日期，人们便会自动参与。然而，实际上并非如此！
虽然你可以依靠这种方式碰碰运气，但实际情况是，黑客马拉松是科技行业中的基石体验，参与者都有自己的期待。不仅如此，你的组织也有特定的需求，并应该为黑客马拉松设定目标。那么，你应该如何保障黑客马拉松对你的组织和参与者都有益呢？
成功的黑客马拉松，取决于一系列可能会反复出现的决定。关于你想达成什么目标的决定，将影响你使用哪些资源以及采用何种沟通方式。这些决定将影响你是选择线上还是线下进行，而这个决定又将反过来影响你需要的资源以及如何沟通。对齐黑客马拉松的计划并非只是让人们达成共识那么简单。你需要一整套内在的决策来达成一致。例如，一场技术难度较高的黑客马拉松可能无法吸引大量观众（你可以问我怎么知道！），并需要一种需要特殊资源的招募策略。
这些年来，我主办过很多次黑客马拉松，包括最近几个月中，在我所在的组织主办的一次黑客马拉松，由此催生了我们将融入到我们的开源产品 Traefik Proxy 3.0 下一版本中的新特性。因此，相信我，策划一个能丰富参与者体验，同时为你的项目创造有价值成果的黑客马拉松，不仅仅需要期待、披萨，和混乱！
本文以最近的 Traefik Labs 黑客马拉松为蓝图。我分享了一个清单，提供了一些技巧和窍门，帮你确定目标，规划比赛，管理报酬，分享你的成果，以及处理黑客马拉松的长期效应（黑客马拉松结束后的工作并未结束！）
这个指南充当了你规划最佳实践的模板，让你也能成功举办一场有大量目标受众并能带来实效的黑客马拉松！
### 1、确定目标的三个问题
首要且至关重要的步骤就是设定你的目标。这可不简单，设立目标前你需要在多个方面进行内部整合，提出如下问题：
- 你为何想举办一场黑客马拉松？
- 你期望谁来参加？
- 你将如何衡量你的成功程度？
#### 确定你的内部利益相关者并设立期望
**黑客马拉松涉及到多个功能部门**。没有一个黑客马拉松是由一个社区人员独自进行的。确保每个人对目标的理解、实现这些目标所需的要求相互呼应，以及必要的资源能得到投入，这些都是重要的。听起来可能有点过于“公司化”，但即使在最小的项目中，这些功能也是必不可少的。一个项目需要广泛的接受度和代码支持。它还需要根据使用者的来做出价值判断。当然，无论何种项目都需要热情的贡献者。
**黑客马拉松需要跨各功能部门的资源投入**。单一团队拥有的一整套资源并不能成功地运行一场黑客马拉松。组织必须投放各种资源，包括：
- 市场营销部门进行规划和拓展。
- 产品管理部门提供产品和行业特定的洞察。
- 工程部门提供深度的技术知识和社区参与。
出于这些原因，黑客马拉松通常会支持满足跨功能部门的目标。例如，你的社区团队可能希望建立归属感并将用户转变为活跃的社区成员。营销团队可能希望提高知名度并吸引新用户。工程团队可能需要特定需求或挑战的新视角。产品团队可能对社区应该知道的目标或禁止行为有特定的设想。
最后但同样重要的点，黑客马拉松的预算也需要各部门共同承担。很抱歉告诉你，黑客马拉松并非天上掉下来的！你最大的支出始终是你团队成员的用心投入。
### 2、你为什么要这么做？
设定你的目标是举办成功黑客马拉松的核心部分。如果你对自己想要做什么或黑客马拉松为何重要都不清楚的话，最好情况下，它会浪费大量的潜力；最糟情况下，它将会变成一团混乱。
社区以归属感为动力。你需要决定自己期望从社区得到什么以及你希望社区成员拥有哪些归属感。如果没有清楚的理解这些，你的黑客马拉松可能无法最大程度地赋权于你的社区。
你需要特别关注你的黑客马拉松的设计和目标。不同类型的黑客马拉松吸引了不同技能水平的人。如果你期待的代码很深奥，那么花费额外的时间来倾听合适的受众，并认识到这样会降低整体的参与度。如果你期待的贡献在技能和经验上可以变化，那么你可能需要拓宽接纳的范围。
#### 你是否举办黑客马拉松来获取代码并推进你的项目？
- 有时，项目处于关键时刻或者围绕它有很多兴奋点，你希望利用这股力量共同创造一些事情。黑客马拉松正是一个达成这个目标的好方式！
- 如果你拥有一个活跃的用户社区，黑客马拉松可以将每个人同一时间共聚一堂，以此激发团队的创造能量。
**注意**：较小的，彼此互相关联并共享项目经验的团队确实更易实现这一目标。你还需要仔细评估构建你的项目所需的技能.
#### 你举办黑客马拉松的目的是建设你的社区或者重新唤起他们的热情吗？
- 可能你正在建设你的社区，或者你注意到你的社区需要一些新的活力。黑客马拉松带有激动人心的氛围，它们可以帮助恢复这种活跃度。
- 正如我在上文所说，“社区是以归属感为动力的。” 如果社区成员感觉他们在这个社区中没有足够的归属感，或是他们的需求和声音没有被重视，他们将会渐渐疏离。这在项目逐步扩大并更加正式化时往往会发生。随着参与的门槛不断提高，社区成员归属感的下降，项目对用户而言就更像是一种产品。提高社区参与感的一种方式是，举办引入用户并降低参与门槛的活动：比如错误修复活动、轻型需求、及长期的活动时间线。
- 或许正如你的用户社区在壮大，但由于技术日益复杂，与之相应的贡献者社区也变得更为专业化。在这种情况下，你需要吸引理解你的技术和使用者的复杂技术领域的人才。你应该寻找那些在工作中使用你技术的社区成员 —— 尤其在有大型或复杂部署的公司。这些人更有可能理解用户的需求以及技术本身的要求。他们也会对重大且有价值的优化提出建议。
- 你可以选择那些能建设你的社区，同时符合你的团队和社区成员的能量和时间的目标。例如，对于 Traefik Labs 来说，一个面向热心人士的、需要较小时间投入的黑客马拉松可能会针对我们的插件目录。然而，当我们在寻找较大贡献或是需要深度专业知识的贡献者时，我们可能会关注高级技术人才 —— 特别是我们认识的人。
#### 你是以庆祝某个事情为目的来举办黑客马拉松吗？
- 黑客马拉松是庆祝新产品发布和激发社区热情的有效方式。例如，这正是我们举办 [Traefik Proxy 3.0 Hackaethon][12] 的原因。
- 黑客马拉松也适合推广新产品的功能。在此，[Traefik Plugin Hackaethon][13] 便是一个很好的例子。
- 或许你想要举办一个活动来纪念你的顶级贡献者。那就用黑客马拉松来做吧！瞧瞧 [HackerOne 组织的这场黑客马拉松][14] 吧。如果你在思索：“但这并非与开源软件相关，这怎么能算是黑客马拉松呢？”我要告诉你的消息是 —— 黑客马拉松不只是为了开源软件！黑客马拉松是为了与广大的社区共创。
#### 你是为了提升知名度而举办黑客马拉松吗？
如果你刚起步并想提高你的产品/品牌知名度，黑客马拉松无疑是个好的开端。然而，请注意一些条件。
- 在这个阶段，期望目标高度集中或收到大贡献是不太可能的。你应追求更广泛而温和的焦点，并尽量减少参与者所需的工作。
- 尝试接触新的社区成员、经验相对较少的用户，以及对你特定项目接触不多的用户。
#### 你是为了与用户建立联系而举办黑客马拉松吗？
我认为没有比举办黑客马拉松更好的办法来将新用户引入你的项目。用户不仅会对你的项目有深入的了解，黑客马拉松也具有一种独特的方式，能够营造出一种难以通过其它类型活动实现的归属感。
### 3、你的目标观众是谁？
假设你已经确定为何要举办黑客马拉松以及你期望实现的目标，那么接下来该评估参与者需要具备哪些特性才能成功了。根据你设定的目标，明确你的目标受众，搞清楚哪一类社区成员能帮你实现这些目标。你可以根据以下几个对比进行考虑：
- 高级技能 vs. 混合技能 vs. 初级技能
- 专门技能 vs. 广泛技能
- 高强度时间投入 vs. 低强度时间投入
- 个人贡献 vs. 团队贡献
你最活跃的社区成员应该在某种程度上与你的目标观众有所呼应。
如果你能吸引到的观众和你的目标观众至少有 80% 的不符合，你可能需要重新考虑你的目标。准确识别你的目标受众对于构筑你的黑客马拉松及相关沟通策略，并让你的黑客马拉松更加成功极其重要。
### 4、你计划如何衡量目标的实现程度？
很好，你已经回答了前两个重大问题并明确了你的目标，接下来要考虑的是第三个重大问题 —— 你打算如何评估目标的实现程度？激励内部团队与社区一同构建你的项目的未来，激发归属感和提升参与度，这些都十分重要，但你无法断定成功与否，如果你没有评估目标的方法。
#### 活动结束后，什么标志着成功？
- 显然，首要的成功标志是你的参与者整体获得良好的体验，并且愿意更加积极地参与你的项目。
- 如果你在寻求扩大影响力，你可以设定一个参与者人数的目标，并且设定一个在活动后或三个月后再次参与的人数目标。
- 成功的一大标志是参与者是否在黑客马拉松期间互相连接、交互、共享知识，并组建团队。
- 是否形成了指导关系？通过合作，是否有许多新的用户转变为熟练的中级用户，或者中级用户升级为专家级用户？这是成功的关键标志。
- 你的合作机构（比如大学）是否要求在未来举办更多的黑客马拉松或其他活动？
- 如果你在提升知名度，也可以关注活动后的讨论情况。有谁写了博客文章？参与者在社交媒体上谈论了吗？
- 如果你在寻找贡献，贡献是否在你预期范围内？这些是你需要的贡献吗？它们是否影响了你的团队对问题的思维方式？你会和这些贡献者建立持久的合作关系吗？
#### 活动过后三个月，什么标志着成功？
设定长期成功的基准也同样重要。以下是可能显示长期成功的一些例子：
- 你的黑客马拉松应当增多持续为你的项目做出贡献的人。目标在于让人们对你的项目保持热情。如果新来的人从黑客马拉松开始并保留下来成为用户，或者你的现有用户变得更加活跃，你就算赢了。
- 黑客马拉松作为单独的事件很棒，但作为营销内容，它更具价值。这些活动在社区中建立了信任，彰显了你的反应以及你重视社区的投入。它们运营的趣味性成为了社区成员的聚焦点，并激发他们对未来的期待。人们喜欢看到他人被庆祝，并计划在将来取得这种成绩。
- 当你围绕你的黑客马拉松制作营销内容时（或最好，别人为你的黑客马拉松制作内容），你就可以扩大你在二度联系人群中的影响力。
- 以羡慕他人为耻的现象是令人遗憾的。黑客马拉松是个绝佳的机会，可以邀请那些表现杰出的参与者去做更酷的事情，并宣传你的项目。
### 5、决定是线下活动还是线上活动
我猜你可能在思考 —— 线下活动是否还在我们的选择范围内？在后疫情时代，我们已经习惯于线上进行所有活动。那么，线下活动的时代就此结束了吗？我会争论说，不，线下活动依然在。只要我们采取适当的防护措施，线下活动仍然是黑客马拉松的精髓。（LCTT 译注：此文发表于半年前。）
- 线下活动意味着无干扰、丰富的披萨，以及充足的能量饮料激发的友谊。
- 线下活动更倾向于促进团队参与，而不仅仅是个人参与。
- 线下活动无论规模大小都适应：对大规模群体组织线下活动会带来高能量和奖励。但这会造成较高的成本。如果你计划举办大规模黑客马拉松，相对经验较少的开发者（如学生、社团、新入职者）将是更好的目标，因为这些人有更多的时间，并且在展示他们的技能和热情时有着更大的收获。
- 线下活动也很适合小的团队，非常适合紧张的计划和迭代 —— 和新老朋友一起度过的长夜，通常是吃着食物和喝着啤酒！
当然，虽然线下黑客马拉松有很多优势，但这并不是说线上体验只有缺点。诚然，没有什么能替代深夜聚会佐以披萨，即兴的评论让你改变整个项目方向，以及你正在测试或调试时，一双友好的眼睛注视着你的感觉。然而...
- 线上活动意味你可以吸引更广泛的参与者群体，且成本大幅减低。
- 线上活动尊重残障人士。
- 线上活动不受地理位置约束。
- 线上活动为个人做出更多贡献提供了更大可能。
- 线上活动在活动形式和时间长度上提供了更多灵活性 —— 毕竟你不能办一个持续一个月的线下活动！
#### 线上黑客马拉松的时间安排
决定举办线上黑客马拉松了？很好！现在你需要确定你期望的线上黑客马拉松类型。你是想要一个持续时间长的还是一个强度大的？请记住，你选择的 [线上黑客马拉松][15] 的类型会在某种程度决定你的目标观众和沟通策略。
**延长的时间线：**
- 允许参与者在工作之外的时间投入，因此开发者可以不请假就参加。
- 提供更多时间来征求贡献。
- 对于组织者和参与者都需要较少的资源投入。
- 延长的时间线需要较少的实时资源。
**紧凑的时间线：**
- 重现了那种在线下黑客马拉松中通常体验到的紧张感。
- 在短时间内需要大量的资源。
- 需要严格的管理和沟通平台。
- 需要清晰的一对一沟通，但也可以促进群体对群体或社区内部的沟通。
### 6、构筑你的沟通策略
谈及沟通，确定了目标后，你需要决定**谁**将与参与者沟通以及**如何**进行沟通。通常，我们需要在流行应用中进行选择。你的选择将对活动的氛围产生影响。不同的 [聊天应用][16] 和 [协作平台][17] 都具有各自的文化和优势。你在初期关于如何举办你的黑客马拉松（线下或线上，长期或紧凑）的决策，可能会对你的沟通策略产生最显著的影响。
#### 线下沟通计划
如果你正在举办一个线下的黑客马拉松，可以将其视为一个重要的活动 —— 它几乎感觉如同一场会议。线下的黑客马拉松通常包括以下活动：
- **研讨会 / 圆桌讨论**：意在教育并建立面对当前需求的新一代标准 / 最佳实践。这些环节可以作为 6 至 10 人间的限时讨论，他们会一致同意研究结果并向所有参与者公开记录的内容。
- **规划会议**：常用于产出非编程类的项目，比如制定更新标准。
- **编程会议**：用于需要持续工作以持续进步的编程类项目。
以上每一环节都有各自的沟通需求：
- 有人准备来引导，但不主导研讨会中的对话。
- 记录者以及确保笔记整理为可发布内容的人。
- 对于研讨会：
- 项目经理来保证所有工作的执行。
- 管理活动的通用沟通（如食物、清洁、资源管理）。
- 主持人负责推动活动议程。
要完成所有这一切，需求来自于你的社区，产品经理和技术团队的资源和专门知识。从过去的经验来看，，要管理如此规模的活动，需要一个由社区成员和员工组成的团队。为了成功，你的团队将需要专业特长的人员。
你还需要决定你想要鼓励的沟通类型，以及谁应该负责：
- 多个团队可能需要轮班以提供全方位的支持。
- 开发者关系团队、工程或支持团队需负责管理与参与者和中间环节之间的技术沟通。
- 社区团队通常会花费很多时间建立与参与者的联系，以帮助他们强化技能或观点，这也是确保黑客马拉松魔力的一种方式。
- 社区团队还需要支持市场营销活动，以吸引参与者并进行后续管理。
#### 线上沟通方案
对于网络虚拟的黑客马拉松，选择沟通平台主要取决于你想实现的目标，你为黑客马拉松选择的时间表（延长或密集），以及你希望促进的沟通方式（同步或异步）。
**在 Git 主机上使用拉取请求和议题（异步）：**
- 选择通过 Git 拉取请求和你项目的议题进行交流，可以把对项目的讨论保留在你当前的流程中，让你的团队更专注响应，而不用自发去引导沟通，这将会节省技术团队的资源。
- 如果你的黑客马拉松团队规模较小，或者预期的贡献相对较少，且你没有计划协助参与者组建团队，那么这种方式非常合适。
- 对于持续时间较长的黑客马拉松，使用已有的流程尤其有益，因为它们不需要额外的管理，也不需要你的团队去监控另外的应用。
- 然而，缺点在于你只是促进了已经协同工作的个别贡献者或贡献者团队的沟通。连接孤立工作的参与者比较困难，参与者们自行寻找彼此也不容易，这就失去了黑客马拉松参与者在公开的讨论中自发交流的魅力。
**使用聊天应用（同步）：**
- 选择专用聊天服务器对于密集型的黑客马拉松是必须的。
- 聊天促进了团队的组建和对于有快速时间线的复杂项目必要的沟通，并激发了在做出了一些很棒的贡献前的头脑风暴。
- 再者，你的目标是要建立社区。人们想要加入一个他们可以有归属感、有朋友、感到舒适的社区。如果你希望他们长期留存，给参与者提供一个可以相互联系的地方是必要的。
- 事件结束后聊天服务器依然存在，可以持续促进社区的参与活动。
不论你选取哪一个平台，你都需要一个沟通方案来确定你的团队每个人何时在线。管理一个线上黑客马拉松可能会有点复杂，主要是因为不同的时区的问题 —— 人们可以在任何他们想要的时间、任何他们想要的地方参加。你必须计划安排在所有时区的人和每一个场合的参与者。排列好一个计划，清楚在下列情况下谁负责以及何时负责：
- 确定响应 SLA。
- 活跃你的虚拟空间（一个死气沉沉的空间会导致沟通质量降低）。
- 鼓励团队建设。
- 解答技术问题。
- 查询参与者的进度。
- 检查空间以确保参与者的安全。
### 7、确定奖项
你的黑客马拉松是一个竞赛形式的活动吗？通常，黑客马拉松的参与者对于优秀贡献者能获得大奖和丰富的礼品会感到非常满意。但在你决定这些令人兴奋的奖励（实物奖品）之前，你必须确定你的竞赛所重视的价值。
- 是什么因素让一个贡献变得更出色？如果你的参与者了解你对此的态度，他们可能更有可能全力以赴。
- 你重视什么？这是你向参与者阐明你希望看到什么样的参赛作品的机会，你可以通过把奖品挂在它旁边来做到这一点。例如，在上次的 Traefik 黑客马拉松中，我们为最受欢迎的特性提供了奖赏，实际上，这些特性确实是大多数人最努力的部分。
- 参赛作品是否有不同的分类？你需要为每个分类都设定奖项。
- 创造一个评分标准（定义和排名成绩的表格或网格，[像这个例子][18]）。这样一来，参与者会知道你在评估他们时重视什么。这也是我们在 HackerOne 提高提交质量的一种方式。
另一方面，有些人可能认为竞争被高估了。如果你的目标是鼓励参与，那么你有权奖励每一个参与者，只因他们为社区的回馈！[Hacktoberfest][19] 就是这种方法的一个好例子。
### 8、准备炫酷的礼品
每个人都喜欢炫酷的礼品！无论是在线活动还是线下活动，你的参与者肯定会欣然接受能够纪念这次活动的礼品。礼品有两个目的：
- 礼品表示你对参与者的赞赏：贡献者花费时间投入在与你的紧密合作中，用一份礼品感谢他们就显示出了你对他们贡献的价值认同。
- 礼品增加了知名度：给参与者分发礼品，帮助他们传播他们对于社区的喜爱，并通过分享他们的收获和经验，提升你的社区的认知度。
社区成员喜爱礼品，但他们不喜欢单调的礼品！也许你在其他活动中已经发放过你现有的 T 恤和贴纸了。想让你的黑客马拉松给人留下深刻印象，就需要寻找新的、有趣的、专有的设计。T 恤固然好，但卫衣则更胜一筹。但是，你可以考虑一下参与者可能还没有的独特礼品。想象一下有什么可以成为他们的新宠，比如后备电池或帽子（这两样在 HackerOne 很流行）。对我个人来说，我家里就有一些来自黑客马拉松的毛巾和拖鞋！
### 9、进行宣传
设定目标和决定惊人的大奖和炫酷的礼品都是非常重要的步骤。但如果你不进行广泛的宣传，怎么能让人们知道你的黑客马拉松正在进行呢？你需要仔细调查可用的各类渠道，并要大胆地推广你的活动。这里说的包括博客、视频博客、电子邮件、社交媒体 —— 任何你能够利用的平台。
然而，依据你的目标定位，你需要在适当的渠道上进行投入。你进行广告的地方，取决于你想邀请谁来参加你的黑客马拉松。
- 如果你想吸引更有经验的用户，那么就将重点放在正在使用你的项目的大型组织上。在这种情况下，领英和电子邮件推广可能会更有效。
- 如果你希望吸引新的和经验较少的用户，那么你最好瞄准大学和培训营。在基于社区的媒体上宣传活动，如 Mastodon、Matrix、Mattermost、Reddit、Discourse、Discord，以及你的目标听众常去的任何地方，将是更好的选择。
### 10、后期管理
恭喜，黑客马拉松结束了！现在所有与黑客马拉松相关的活动都可以暂时停下，我们也不再需要投入资源了，对吗？错！你要把黑客马拉松视为你在软件开发和社区构建一系列活动中的一个环节。为了让你的黑客马拉松成功，你必须准备好进行活动后的各项工作。
- 传达你的成果：别忘了向内部和外部通报黑客马拉松的结果。在黑客马拉松期间，社区成员获取的成果可以增加对你的社区和项目的信任。
- 社区建设：依赖你的黑客马拉松参与者进行未来的社区活动。
- 编制回顾：什么做得好，什么做得糟糕，哪些事情让你感到平淡无奇，又有什么事情让你感到惊讶？这个分析是你如何成长，变化和迭代的方式。在可能的情况下，尽快做一个无责任的回顾，这样所有的事情还鲜活在你的记忆里。
### 总结
如果你一开始读这篇文章时，认为举办黑客马拉松并不难，那么我很遗憾要打破你的幻想！虽然我深信黑客马拉松是一个极好的方式，可以在多个层面上与社区进行交流和互动，但只有意图并不能保证结果。
为了使一个黑客马拉松成功，你需要非常周到，并准备投入大量的资源和努力来妥善规划和执行。
感谢你的阅读，我希望这个清单能帮助你成功地组织你的下一场黑客马拉松！
*（题图：MJ/954f2da1-8a3a-4039-9695-b7ea7e3dea95）*
--------------------------------------------------------------------------------
via: https://opensource.com/article/23/2/hackathon-guide
作者：[Tiffany Long][a]
选题：[lkxed][b]
译者：ChatGPT
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/tiffany-long
[b]: https://github.com/lkxed/
[1]: https://opensource.com/article/23/2/hackathon-guide#set-your-goals
[2]: https://opensource.com/article/23/2/hackathon-guide#why-are-you-doing-this
[3]: https://opensource.com/article/23/2/hackathon-guide#who-is-your-audience
[4]: https://opensource.com/article/23/2/hackathon-guide#how-are-you-measuring-goals
[5]: https://opensource.com/article/23/2/hackathon-guide#decide-on-in-person-vs-virtual
[6]: https://opensource.com/article/23/2/hackathon-guide#build-your-communication-strategy
[7]: https://opensource.com/article/23/2/hackathon-guide#decide-on-the-prizes
[8]: https://opensource.com/article/23/2/hackathon-guide#swag-it-up
[9]: https://opensource.com/article/23/2/hackathon-guide#get-the-word-out
[10]: https://opensource.com/article/23/2/hackathon-guide#managing-the-long-tail
[11]: https://opensource.com/downloads/hackathon-guide
[12]: https://traefik.io/blog/announcing-traefik-proxy-3-0-hackaethon/
[13]: https://traefik.io/blog/announcing-the-inaugural-traefik-hackaethon-2020-in-october/
[14]: https://www.youtube.com/watch?v=9VZCD9TirCg&list=PLxhvVyxYRvibM_KJBPtPsfEcjnP5oGS8H
[15]: https://opensource.com/article/20/8/virtual-hackathon
[16]: https://opensource.com/alternatives/slack
[17]: https://opensource.com/article/21/9/alternatives-zoom
[18]: https://www.isothermal.edu/about/assessment/assets/rubric-present.pdf
[19]: https://hacktoberfest.com/
[0]: https://img.linux.net.cn/data/attachment/album/202309/11/091824uz1hs6l2c16s662r.jpg