Open source software is at the heart of everything we do at Open Tree Technology Lab. From the Kubernetes clusters that run our workloads to the terminal emulators our engineers use every day — our stack is built on open source. Here’s how we approach OSS and why we actively contribute back.
Why We Maintain Forks
If you browse our GitHub organization at github.com/opentreecz, you’ll find forks of projects like Ghostty, Kitty, Alacritty, K3s, OpenWrt, and Chiaki. We don’t fork for the sake of it — each fork serves a purpose:
- Custom patches: Sometimes we need a fix or feature before it lands upstream. Our forks let us move fast while still contributing patches back.
- Specialized builds: Our OpenWrt fork, for example, includes configurations tailored to our network infrastructure.
- Testing and validation: Forks give us a staging ground to test changes before proposing them upstream.
Our Own Tools
Beyond forks, we build and maintain our own tools. openrepo and openrepo-sync are repository management tools written in Python and Rust respectively. They help us keep our Git mirrors synchronized across platforms and automate repository lifecycle management.
Contributing Upstream
We believe that using open source comes with a responsibility to contribute. Bug reports, documentation improvements, and code contributions all flow upstream from our team. It’s not just altruism — it’s good engineering. The healthier the upstream project, the less maintenance burden on our forks.
Building in the Open
Transparency builds trust. By publishing our tools and configurations openly, we invite scrutiny, collaboration, and improvement. It also helps us recruit — talented engineers want to work with teams that contribute to the community.
Check out our repositories at github.com/opentreecz and feel free to open an issue or submit a pull request. We’d love to collaborate.
Napsat komentář