RunWhen Authors Introduction

We believe that engineers thrive when their hard-earned expertise is shared widely, so that everyone—no matter where they are—can benefit from it. At the core of our platform and our FOSS offerings is our community of authors, who freely contribute and exchange troubleshooting know-how, code snippets, and domain-specific knowledge. In doing so, they help forge an open, ever-evolving ecosystem that any engineer can tap into or subscribe to—putting the power of collective expertise in everyone’s hands.

Our mission is to build the world’s largest open collection of automation code, with testing, documentation, and metadata that rival even the biggest hyperscale companies. While it’s nearly impossible for most organizations to match these massive efforts on their own, an open-source community can do exactly that. By combining our strengths, we can achieve something greater than the sum of our individual contributions.

If this sounds exciting, we’d love to have you join our community. Below is a quick glossary of our key concepts, along with details on how to get started as an author and information about our rewards program. Feel free to reach out to us on Slack if you have any questions.

Author CodeCollection Development Overview

CodeCollections

CodeCollections are version-controlled repositories following a consistent file structure. They house collections of “CodeBundles,” which are the core building blocks across our ecosystem. Both RunWhen Platform and RunWhen Local can index and use these collections, making them the primary source of functionality.

https://registry.runwhen.com/all_codecollections/

CodeBundles

CodeBundles package source code, metadata, and dynamic configuration together to perform specific actions. Most frequently, they include Python, Robot Framework, and bash components. CodeBundles serve as the basis for SLIs, SLOs, and TaskSets on the platform, and also wrap commands with metadata for use in RunWhen Local.

https://registry.runwhen.com/CodeCollection/rw-cli-codecollection/azure-appservice-triage/

Troubleshooting Commands

Many CodeBundles begin with troubleshooting commands, enriched by metadata and configuration. But they can also include an array of other valuable assets—from software development best practices, to language-specific scripts and frameworks, to even business workflows and automations. If you have frequently used commands or code snippets you’ve been keeping in your personal notes—or if you’re looking for new ideas and patterns for anything from Python or Java libraries to Redis and Kubernetes—head over to our community discussions. You can freely share your own work, adopt what others have published, and subscribe to ongoing updates. These solutions are all compatible with our FOSS tool, RunWhen Local, so you and your entire team can build on each other’s expertise.

Contributing

We’d love to collaborate with you as part of our community. Head over to our contributing doc to learn more about how to get started, our author rewards program, and how your expertise can help others worldwide.

Communication

You can connect with us on our public Slack to get in touch. We look forward to seeing what you’ll build and share—and we can’t wait to learn from your expertise as we work together to create a more powerful, open, and collaborative future.