Skip to content

GOVERNANCE.md

Latest commit

 

History

History
119 lines (84 loc) · 4.57 KB

GOVERNANCE.md

File metadata and controls

119 lines (84 loc) · 4.57 KB

LabOS Contributor Governance & Incentive Program

LabOS 贡献者治理与激励机制

🏛️ Project Governance | 项目治理

Roles | 角色体系

Role Requirements Permissions
Maintainer (维护者) Project creator Full access, final decision on all PRs, roadmap control
Core Contributor (核心贡献者) 10+ merged PRs or 1 major feature Write access to main repo, review & merge PRs, vote on roadmap
Contributor (贡献者) 1+ merged PR Listed in README and Contributors wall, access to contributor channel
Community Member (社区成员) Star, issue, or discussion Participate in discussions, submit issues and PRs

Decision Making | 决策流程

  • Minor changes (bug fixes, docs): any Core Contributor can merge
  • Major features: require Maintainer approval
  • Architecture changes: discussed in Issues first, require consensus

🏆 Incentive Program | 激励机制

Tier 1: Recognition | 荣誉认可

Every merged PR earns you:

  • 🏅 Name + avatar in the Contributors Wall in README
  • 📜 Contribution badge on your GitHub profile (via GitHub's contributor graph)
  • 🎖️ Role upgrade path: Contributor → Core Contributor → Co-Maintainer

Tier 2: Premium Access | 高级权限

Active Contributors (3+ merged PRs) get:

  • 🔑 Free access to the Premium Skill Library (when launched)
  • 🧪 Early access to new features and beta releases
  • 📋 Priority issue handling — your bug reports and feature requests are handled first

Tier 3: Revenue Sharing | 收益分成

Core Contributors (10+ PRs or 1 major feature) are eligible for:

  • 💰 Revenue share from Skill Library sales that use their contributed methodology
    • If you contribute a research methodology or experiment template that becomes a paid Skill, you receive 30% of net revenue from that Skill's sales
    • Example: You contribute a "Hierarchical Memory + UCB Retrieval" pipeline template → it's packaged as a paid Skill → you get 30% of each sale
  • 📝 Co-authorship on any research papers that use your contributed pipeline/methodology
  • 🎓 Reference letters from the Maintainer for academic or job applications

Tier 4: Bounties | 悬赏任务

Selected issues will carry bounties:

  • Issues tagged with 💰 bounty have a monetary reward (paid via crypto or Sponsors)
  • Bounty amounts are listed in the issue description
  • First accepted PR for a bounty issue claims the reward
  • Bounties will be funded from project revenue and sponsor contributions

📊 Contribution Tracking | 贡献追踪

We track contributions transparently:

Type How it's counted
Code PRs Merged pull requests
Documentation Docs PRs, README improvements, translations
Bug Reports Confirmed bugs with reproduction steps
Community Help Answering questions in Issues/Discussions
Research Contributing experiment templates, methodologies, benchmarks
Design UI/UX improvements, visual assets

All types count equally toward role upgrades. Code is not the only way to contribute.

所有类型的贡献在角色升级时同等计算。代码不是唯一的贡献方式。

🤝 Code of Conduct | 行为准则

  • Be respectful and constructive
  • Welcome newcomers — everyone was new once
  • Give credit where it's due
  • Disagree on ideas, not on people
  • Write clear commit messages and PR descriptions

📅 Roadmap Participation | 路线图参与

  • Monthly: Maintainer posts a roadmap update in Discussions
  • Core Contributors can propose and vote on next priorities
  • Anyone can suggest features via Issues

🔄 How to Level Up | 如何升级

Community Member
    │ (submit your first PR)
    ▼
Contributor ──────────────────────────┐
    │ (10+ merged PRs                │
    │  or 1 major feature)           │
    ▼                                │
Core Contributor                     │
    │ (sustained contribution        │ ← Revenue sharing
    │  + community leadership)       │ ← Skill Library access
    ▼                                │ ← Bounty eligibility
Co-Maintainer ───────────────────────┘

This governance document is a living document and will evolve as the community grows. Suggestions for improvements are welcome — open an Issue or PR.

本治理文档会随社区发展持续更新。欢迎提出改进建议。