From 534da7f9caf63f9d74548a4f1279082c89b56ed2 Mon Sep 17 00:00:00 2001
From: Xingyu Wang <xingyu.wang@gmail.com>
Date: Mon, 11 Sep 2023 09:20:25 +0800
Subject: [PATCH] ATRP

@wxy
https://linux.cn/article-16179-1.html
---
 ...¸�â­�ï¸� A 10-step guide for a successful hackathon.md | 305 ------------------
 ...¸�â­�ï¸� A 10-step guide for a successful hackathon.md | 297 +++++++++++++++++
 2 files changed, 297 insertions(+), 305 deletions(-)
 delete mode 100644 sources/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md
 create mode 100644 translated/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md

diff --git a/sources/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md b/sources/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md
deleted file mode 100644
index 5514488bd7..0000000000
--- a/sources/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md	
+++ /dev/null
@@ -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/
diff --git a/translated/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md b/translated/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md
new file mode 100644
index 0000000000..0df88b8241
--- /dev/null
+++ b/translated/talk/20230213.1 ������ A 10-step guide for a successful hackathon.md	
@@ -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
\ No newline at end of file