How Taro Structures Contributor Promotion and Governance

To build a more complete and sustainable Taro open‑source ecosystem and highlight contributor value, the project has established a Contributor Promotion System that offers clear participation and honor incentives for developers and contributors.

Promotion Roles

The system defines four promotion paths:

Individual Contributor → Assistant → Collaborator → Technical Steering Committee member

Individual Contributor → Collaborator → Technical Steering Committee member

Ecosystem Individual Contributor → Ecosystem Collaborator → Technical Steering Committee member

Inactive contributors for a year are automatically demoted, while outstanding contributors may apply for retirement status.

Individual Contributor & Ecosystem Individual Contributor

Any developer who agrees to the Taro Code of Conduct can submit pull requests, bug reports, fixes, or new feature proposals following the Contributor Guide . Their contributions are listed in the Taro official documentation as individual contributors. Those creating tools, plugins, tutorials, or training around Taro are listed as ecosystem individual contributors.

Assistant (Triage)

Assistants maintain new issues in the NervJS/taro and NervJS/taro‑ui repositories, label issues and pull requests, comment, close or reopen them, and route bugs or features to the appropriate working groups.

Purpose: Reduce issue backlog, keep issues tracked, and encourage new contributors.

Benefits: Github NervJS group Member rights and Triage rights on the projects (no write access).

Application: Submit a pull request to the README.md of the Taro project explaining the motivation and agreeing to the code of conduct; approval by two collaborators is required. The template is shown in the image below.

Exit: Assistants inactive for six months are regularly removed.

Collaborator & Ecosystem Collaborator

Collaborators maintain the NervJS/taro and NervJS/taro‑ui repositories, assist users and junior contributors, join specific working groups, and review issues and pull requests.

Purpose: Continuously enrich Taro features, performance, and security.

Benefits: Github NervJS group Member rights and Write access to the repositories, ability to configure CI tasks, and merge pull requests (a PR requires at least two collaborators or one technical committee member to approve; after a three‑month observation period the collaborator becomes official).

Application: Outstanding individual contributors are nominated; voting decides promotion. Candidates must demonstrate technical depth, business expertise, clear communication, good character, humility, and an owner mindset. The pull‑request template is illustrated in the image below.

Exit: Inactive collaborators may be removed or set to retirement by the technical committee; after six months of no contributions, they are automatically retired but can reapply for active status.

Technical Steering Committee Member

Members guide technical direction, project management, releases, contribution policies, repository hosting, code of conduct, and maintain the collaborator list. The chair hosts online meetings, records minutes, and publishes them.

Purpose: Resolve technical challenges and set new directions that lack consensus.

Benefits: Github NervJS group Owner rights.

Application: New members are nominated by existing committee members and elected by vote. The pull‑request template is shown in the image below.

Exit: Members absent from 75% of quarterly meetings and who have not voted in any meeting are automatically removed; members may request temporary retirement.

Operation Mechanism

The technical committee and five sub‑teams (Core, Plugins, Platform, Innovation, Community) form the governance structure. Each team has owners responsible for development progress.

Teams

Core Team

CLI Working Group – develops and maintains the Taro CLI.

Compile Working Group – maintains and optimizes the compilation system for mini‑programs and H5.

Runtime Working Group – maintains the runtime system for mini‑programs.

Plugin Team – maintains Taro plugins, including platform plugins and React/Vue DevTools.

Platform Team – responsible for cross‑platform development (App, Web, Open Harmony).

H5 Working Group – maintains H5 modules, routing, component library, API library.

React Native Working Group – develops core, component library, and API for React Native adaptation.

Open Harmony Working Group – develops HarmonyOS adaptation core, component library, API.

Quick App Working Group.

Innovation Team – explores new directions such as WebAssembly, Rust, Vite, Flutter, Electron, etc.

UI Framework Interest Group – develops and manages UI libraries like TaroUI, NutUI, and other ecosystem tools.

Community Team – handles Taro ecosystem operations and community promotion.

Technical Committee Bi‑weekly Meeting

Schedule: Every other Thursday, announced in the TSC issue with agenda and date.

Agenda: Items labeled with tsc‑agenda from Taro projects. After the meeting, minutes are submitted via pull request. Non‑committee members may attend but have no voting rights.

Consensus‑Based Voting Mechanism

All promotion votes follow a consensus decision principle, aiming for majority agreement.

Topics are announced in advance to give members research time.

Before finalizing, the question “Is anyone opposed?” is asked to give a last chance to object.

If consensus cannot be reached, a vote decides whether to postpone to the next meeting.

Once “majority wins,” the decision passes; members may abstain.

Guidance / Training Mechanism

Assistants, collaborators, and technical committee members receive appropriate guidance and training at each stage to enable new members to start work quickly.