This document describes the transition from Flutter's historical membership system (flutter-hackers with blanket write access and static AUTHORS files) to the tiered contributor ladder.
Existing members are placed according to 12-month activity records:
graph TD
LegacyHackers["Existing flutter-hackers & org members"] --> Analysis["12-month activity analysis"]
Analysis -->|"Googlers & Partners"| Maintainers["Maintainer Tier<br/>(@flutter/googlers, @flutter/partners)"]
Analysis -->|"≥ 30 contributions (≥ 10 PRs)"| Committers["Committer Tier<br/>(@flutter/committers)"]
Analysis -->|"≥ 10 contributions"| Reviewers["Reviewer Tier<br/>(@flutter/reviewers)"]
Analysis -->|"Joined < 12 months ago"| GraceReviewers["Reviewer Tier<br/>(12-month transition grace period)"]
Analysis -->|"< 10 contributions (Inactive)"| Emeriti["Dasher Emeritus<br/>(Alumni status)"]
Members of @flutter/googlers (Flutter team engineers) and @flutter/partners (Canonical engineers and partner team members) are placed in the Maintainer tier. Active community members are placed according to their 12-month contribution history: those meeting the Committer threshold (
As a one-time initial transition policy for the first year after the ladder lands, members who joined flutter-hackers within the 12 months preceding ladder adoption and do not yet meet the 10-contribution threshold retain the Reviewer role for a 12-month transition period (grace_until in data/contributors.yaml). Once this initial 12-month window concludes, standard rolling 12-month criteria apply to all members.
Inactive historical flutter-hackers (flutter-contributors Google Group so they can stay in touch and more easily ramp back up onto the project if and when they choose to return.
To ensure all existing GitHub organization members are categorized, the initial audit reviews all members of the flutter GitHub organization (gh api orgs/flutter/members) and cross-references each account against @flutter/googlers, @flutter/partners, @flutter/flutter-hackers, and 12-month activity data to populate data/contributors.yaml. Untracked active contributors are placed into their qualifying tier (Committer or Reviewer), while inactive organization members and former flutter-hackers (
Historically, repository-level AUTHORS files (flutter/flutter/AUTHORS, flutter/packages/AUTHORS, etc.) tracked individual contributors. Over time, these files became static and difficult to maintain. flutter/contributors now serves as the single source of truth for contributor roles and permissions, while historical AUTHORS files are preserved under legacy_authors/. The active ladder roster is published in ROSTER.md and Dasher Emeriti are listed in EMERITUS.md, both generated from data/contributors.yaml.
data/activity_summary.json aggregates rolling 12-month contribution counts across the 52 weekly snapshots in data/activity/YYYY-Wxx.json, and daily syncs (tool/sync_activity.dart) update the current ISO week activity and recompute the summary automatically.