The results showed a nearly even split: about half of respondents had contributed before, and half hadn’t. Among those who hadn’t, the main blockers were familiar ones: not knowing where to start, not having enough time, or feeling unsure if they were qualified to contribute.
If you’ve been thinking about contributing, the good news is there are plenty of pathways to take, even if you’re short on time or just getting started with Zeek. Here’s how you can make a practical impact and help the community solve real-world problems.
1. Share Your Wins and Use Cases
Short on time? Post a quick note in Slack about something Zeek helped you accomplish—like detecting unusual traffic or speeding up an investigation. Share a quick walkthrough with us on a Community Call, or volunteer to write a short blog post showing how you solved a problem or built a workflow.
Many users want to learn from real examples. Sharing practical use cases sparks ideas, helps others avoid pitfalls, and shows concrete ways Zeek can be applied in real environments. It’s as easy as hopping into #general and hitting “send.”
2. Create a Guide or Tutorial
Turn your Zeek experience into a resource for others, whether it’s a how-to, a quick screen capture, or a step-by-step walkthrough. It could be as simple as showing how you tuned a log, automated a common task, or set up Zeek in your environment.
While the Zeek docs cover the basics, real-world guidance helps others navigate challenges faster. Your example can save someone hours of trial and error and show practical ways to use Zeek effectively. If you’d like to create something, drop a note in the #contribute channel on Slack. We’ll help you to bring it to life.
3. Take on a Technical Task
Found a bug? File a report so it doesn’t slip through the cracks. Have an idea for a Zeek script or package? Publish it to share with others. If you’re a developer, the Contribution Guide has everything you need to get started with PRs, issues, and packages.
Bug reports help the team catch issues early, and packages extend Zeek beyond the core project. Even a small script you wrote for your own network might end up solving the same problem for others.
4. Join the Testing Group
If you like experimenting with new releases, the Testing Group is a great fit. Run pre-release versions of Zeek alongside your live setup and report back what you see—whether that’s smooth sailing, a crash, or something in between.
Testing in diverse environments is what makes new releases stable and reliable. Your feedback directly shapes Zeek’s quality, ensuring the final version works well for the whole community. Learn more about the Testing Group on the wiki.
5. Speak at or Help Run an Event
You don’t have to be a core developer or an expert to contribute at events. Give a talk on how you use Zeek in your environment, run a short tutorial on a workflow you built, or support behind the scenes by moderating, reviewing slides, or promoting an event in your own circles.
Events are where knowledge spreads and connections form. Even everyday experiences can teach someone else a new approach or shortcut. Plus, events are a good time and a fun way to meet other Zeek users (at least we think so!).
What’s next?
These pathways are essential to making Zeek thrive as an open source project, and we’re deeply invested in creating pathways that work for every community member who wants to participate. Don’t wait for the “perfect” moment to contribute—the best way to get involved is simply to start.
If you have questions, want to get started, or need a hand along the way, drop us a message in #contribute on Slack!
RSS - Posts