OpenWrt Project Rules

• The roles within the OpenWrt project are: active members, inactive members, and non-members. There is no core developer group or any other group of specially privileged members.
• Members may voluntarily switch between active and inactive status at any time.
• If a member appears not to be participating in project matters, any active member may request that the non-participating member switch to inactive status. This request must be sent by email to the person concerned, with the openwrt-adm mailing list in CC. If the person either agrees or does not respond within 30 days, they will be moved to inactive status.
• Frequent contributors may become members after a simple approval. Project members are free to propose suitable candidates.

• Active members can request commit access to all repositories.
• The commit credentials of inactive members can be revoked. They will be restored upon their return to active status.

• All active members have the right to vote and are encouraged to liberally exercise this voting right in order to maintain a broad consensus on project matters.
• To propose changes to project matters or the overall development direction, a formal proposal must be sent to the openwrt-adm mailing list. The proposal must clearly describe the suggested changes and include a specific deadline for when the voting period will end. A simple approval is required.
• All active members who participate in the new vote or voted in the past 6 months before the new vote was started are considered active voters. If less than 3 votes occurred in the past 6 months the last 3 votes are considered to determine the active voters.
• For a simple approval, the proposal must achieve a two-thirds majority among the active members who participate in the vote. Additionally, it must receive approval from at least 50% of the active voters, regardless of whether they participated in the vote.
• For a change to these rules, a 75% majority among the active members who participate in the vote must approve, as well as 50% approval from the active voters.
• Neutral votes are considered half-approvals.
• Any votes and decisions will be made public on the project website.

• Project infrastructure should be outsourced to FOSS community operated services whenever possible in order to allow members to focus on actual development efforts.
• Any infrastructure that is operated by the project itself shall be administered by at least three different people to reduce the likelihood of the project getting locked out due to administrators being unreachable.
• Responsible administrators for the various services shall be documented publicly.

• The project will not offer individual email accounts under its project domain for privacy and equality reasons.
• Be nice to each other (formerly known as “Rule 12”)

big change to rules

Add the rule “Be nice to each other” Agreed in the meeting 9 May 2016

Changed wording of the rules and removed typos. Extended infrastructure rule to emphasize the FOSS character of used hosting services, added requirement of documented responsibilities. Agreed upon by 6 of 6 attending and 6 of 8 total people.

Initial draft, agreed upon by 6 of 6 attending people.