Skip to main content
Explore the Board

Community

Remote Valley OS is built by a global community of engineers, designers, educators, and builders. Everyone is welcome. Here is how to get involved.

Ways to Contribute

Code & Hardware

Submit pull requests for firmware, CAD designs, sensor agents, or the dashboard. Look for good-first-issue labels in any repository.

Documentation

Improve operator manuals, translate guides into Nepali or other languages, or write training modules. Good docs are as important as good hardware.

Translation

Help translate content into Nepali, Jumli, Hindi, or other regional languages. Make the blueprint accessible to the people who need it most.

Data & Research

Analyze field data, develop economic models, research adaptation requirements for new regions, or improve sensor data pipelines.

Market & Business

Develop market linkages for Jumla Origin products, design business models for agri-hubs, or build distribution channels for community-made goods.

Regional Adaptation

Adapt the blueprint for a new region — different climate, crops, materials, or cultural context. Write an adaptation guide for future deployments.

How to Start

2
Find an issue labeled good-first-issue or help-wanted
3
Join a discussion — introduce yourself and ask questions in GitHub Discussions
4
Open a pull request — every merged PR earns a place in the contributors list
5
Apply for the accelerator — structured remote contribution with mentoring and recognition

Governance Model

The project is governed by the people who do the work. Roles progress naturally as contributions grow.

Community Member

Participate in discussions, open issues, attend community calls. Everyone starts here.

Contributor

One or more merged pull requests. Can label issues, vote in governance decisions, nominate maintainers.

Module Maintainer

Sustained contributions to a specific module. Reviews PRs, triages issues, mentors newcomers. 12-month renewable term.

Core Maintainer

Cross-module integration, release management, project direction. Nominated by core maintainers, confirmed by 2/3 vote.

Community Representative

Elected by deployment-site communities. Represents local needs in governance decisions. Equal weight to maintainers in votes.

Master Trainer

Certified through the education pipeline. Approves curriculum, certifies operators and technicians. Highest local authority.

Our Standards

All community members are expected to follow our Code of Conduct and Community Guidelines. In short:

Be respectful and constructive
Assume good faith
Default to public communication
Give and accept feedback gracefully
Seek consensus before voting
Disagree constructively — focus on ideas, not people

Start Contributing

Your first PR is one click away. Fork a repo, pick an issue, and join the global team building infrastructure for remote communities.