Contributing to Fuz

[ryanatkn]

Fuz is open source but most of its repos restrict PR creation to only maintainers. This is a heavy-handed approach with some unfortunate downsides, but the goal is to sustain my streamlined processes as I invite contributions of many kinds. The current idea is to emphasize community-sourced ideas over implementations, so designs develop in the open with input from whomever cares. AI assistance has changed the balance to where it's much easier for me to implement a sound design, but that same power has caused many open projects to be flooded with low-effort PRs, and I want to sidestep that whole deal, and instead engage with people in ideation.

Despite Fuz not accepting outside code contributions, anyone can contribute in multiple ways:

• reading and commenting on discussions, issues, and PRs
• opening discussions for everything except bug reports
• opening issues for reproducible bugs, and helping triage them
• making and sharing things with Fuz

Policies may change and feedback is welcome. I hope to build mutual trust with the people who show up interested in the software, and long-term build a team of code contributors too, but I think the shared project of designing _what_ to build is more important and challenging and time-consuming, and it's a good activity to do as a community in public. We use the GitHub discussion boards of the various repos to collaborate, with this fuz.dev one being the main one, and community spaces built with Fuz are planned.

See also the intro post, Introducing Fuz, a zippy stack for autonomy