Open Source Muscles
How MasterFabric uses, contributes to, and releases open source software.
Open Source Muscles
We build and maintain "open source muscles": we use, contribute to, and sometimes release open source software. It supports our quality bar, our hiring, and our standing in the community. This page explains how we engage.
Why It Matters
Open source gives us better tools, faster onboarding, and a shared language with the rest of the industry. Contributing back keeps us aligned with upstream, improves our reputation, and helps us attract people who care about the same things. Releasing our own work, when it makes sense, extends that further.
Use
We prefer open source tools and libraries where they fit. From runtimes and frameworks to CLI tools and infra, we build on solid, community-driven foundations.
Contribute
Fixes, docs, and features go back upstream. We file issues, open PRs, and maintain patches so the whole ecosystem benefits and we stay aligned with upstream.
Release
Selected internal work is open-sourced when it makes sense. Reusable libraries, configs, or docs that others can use strengthen our reputation and hiring.
Our Open Source Projects
We back our approach with real code. Projects from our repositories.
How We Choose What to Contribute or Release
- Contribute — When we fix a bug or add a feature in a dependency, we try to push it upstream. We also improve docs and examples when we see gaps.
- Release — When we build something reusable — a small library, a config, or a doc set — we consider open-sourcing it. The bar is: would this help others and reflect well on us?
Not everything goes public
We do not open-source client work or internal tooling that is sensitive or not generally useful. We focus on pieces that are clearly reusable and maintainable.
What You Can Do
- Use — Prefer solid open source options when they fit; avoid reinventing the wheel.
- Contribute — File issues, send PRs, and maintain patches so we stay close to upstream.
- Propose — If you think something we built could be released, suggest it and we can evaluate together.
Licenses and ownership
Before contributing or releasing, we check licenses and ownership. Client work and proprietary code stay internal unless explicitly agreed otherwise.