## Keyboard shortcuts

Press `←` or `→` to navigate between chapters

Press `S` or `/` to search in the book

Press `?` to show this help

Press `Esc` to hide this help

# Community & Governance

Dao OS is fundamentally a community-driven project. Our success is not measured solely by our technical achievements, but by the vibrant, collaborative, and healthy ecosystem we cultivate. This document outlines the principles and processes that govern our collective work.

## Our Philosophy: Open and Transparent

We are unconditionally committed to the principles of Free and Open Source Software (FOSS).

- Open Development: All work on the core protocol and reference implementations happens in public repositories.
- Open Communication: All major technical and strategic discussions take place in public channels.
- Community Ownership: Our ultimate goal is for Dao OS to be owned and steered by its community of users and developers.

## Our Role: From Architect to Gardener

The initial creators and core contributors of Dao OS see their role as an evolving one.

- In the Early Stages (The Architect): Our primary role is to be the architects—to lay a solid and coherent foundation for the project, define the core protocols, and build the initial tools.
- In the Long Term (The Gardener): As the ecosystem matures, our role will transition from building everything ourselves to tending the garden. We will focus on providing better tools, maintaining the core infrastructure, and empowering the community to build and innovate.

## Ecosystem Strategy: Focus and Ignition

As a project initiated by an individual developer, we recognize that our resources are limited. Attempting to provide equal, first-class support for all possible technology stacks is a path to mediocrity.

Therefore, we adopt a strategy of "Focus on One Point to Ignite the Ecosystem."

Our core team's development efforts will be concentrated on creating one "golden path" that is so efficient and enjoyable that it acts as the primary catalyst to attract the first wave of developers. This chosen path is the Nim Unified Development Kit, which leverages Nim's unique capabilities to build both the WASM backend and Web UI frontend from a single codebase.

This does not exclude other development paths (like Rust + TypeScript or native integrations). They remain fully supported at the protocol level. However, they are considered Community/Advanced Paths, where we rely on the community's strength to build out tooling and best practices.

## How to Contribute

Contribution comes in many forms, and all are valued. You can help build Dao OS by:

- Core Development: Contributing to the `Meta Unit` library and the core protocols in Rust.
- `Dao Implement` Development: Creating new `Dao Implements`, which can include `Facet` (UI) components and `Core` (headless logic) components.
- Documentation & Translation: Improving these documents, writing tutorials, and translating them into new languages.
- User Support & Community Management: Helping new users, answering questions, and fostering a welcoming and supportive atmosphere.
- Design & User Experience: Contributing to the UI/UX design for reference `Dao Implements` and defining design patterns for the ecosystem.

## The Decision-Making Process

Our governance model is designed to evolve alongside the project.

1. Early Stages (Phase I-II): Decisions will be made by the Core Team after open discussion in our public communication channels.
2. Growth Stages (Phase III-IV): For significant changes to the core protocol or architecture, we will introduce a formal RFC (Request for Comments) process.
3. Mature Stage (Future): We are committed to exploring and transitioning to more decentralized governance mechanisms.

## Communication Channels

- GitHub: For all code hosting, issue tracking, and RFC discussions.
- Discord / Matrix (TBD): For real-time community chat, Q&A, and collaboration.