Project Rules

Membership

  • The OpenWrt project has three membership roles: active members, inactive members, and non-members. There is no core developer group or specially privileged members.
  • Members may voluntarily switch between active and inactive status at any time.
  • If a member stops participating, any active member may request they move to inactive status. The request goes via email to that person with the openwrt-adm mailing list copied. After 30 days without response, or with their agreement, they transition to inactive status.
  • Frequent contributors can become members through simple approval. Project members may nominate suitable candidates.

Commit access

  • Active members can request commit access to all repositories.
  • Inactive members’ commit credentials may be revoked, then restored upon returning to active status.

Voting

  • All active members have voting rights and should exercise them liberally to maintain broad project consensus.
  • Project changes require formal proposals sent to the openwrt-adm mailing list with a clear voting deadline and description. Simple approval is needed.
  • All active members who participate in the new vote, or who voted in the past 6 months before the new vote was started, are considered active voters. If fewer than 3 votes occurred in the past 6 months, the last 3 votes determine active voters.
  • Simple approval requires a two-thirds majority among participating members plus 50% approval from all active voters.
  • Rule changes need a 75% majority from participants and 50% from active voters.
  • Neutral votes count as half-approvals.
  • All votes and decisions are made public on the project website.

Infrastructure

  • Infrastructure should use FOSS, community-operated services to let members focus on development.
  • Self-operated infrastructure requires at least three administrators to prevent lockout scenarios.
  • Service administrators and responsibilities must be publicly documented.

Other rules

  • The project does not provide individual email accounts under its domain, for privacy and equality reasons.
  • Be nice to each other.

Changelog

DateChange
2025-12-02Substantial revision of the rules.
2016-05-10Added the “Be nice to each other” rule, agreed at the meeting on 9 May 2016.
2016-04-05Reworded several rules and fixed typos. Extended the infrastructure section to emphasise the FOSS character of hosted services, and added the requirement to document responsibilities.
2016-03-24Initial draft, agreed unanimously by all six attendees.