Repository navigation
docs(rfc): add RFC 740.0000 for contributor ladder - #36
Conversation
| * The broadcast-only `flutter-contributors` Google Group onboarding flow will be finalized with the registration Google Form pinned in `#hidden-chat` on Discord. | ||
| * Remaining legacy `AUTHORS` files across other Flutter repositories will be archived into `legacy_authors/` in `flutter/contributors` and replaced with `CONTRIBUTORS` pointer files. | ||
| * External contributor and code review documentation outside of `flutter/contributors`—including [`Contributor-access.md`](https://github.com/flutter/flutter/blob/main/docs/contributing/Contributor-access.md), [`Tree-hygiene.md`](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md), and [`flutter/.github/CONTRIBUTING.md`](https://github.com/flutter/.github/blob/main/CONTRIBUTING.md)—will be updated to reference `flutter/contributors` and the new ladder tiers. | ||
| * The launch of the Flutter Contributor Ladder and the initial Q4 audit / 30-day community review window will be announced to the contributor community across Discord, GitHub, and the `flutter-contributors` Google Group. |
There was a problem hiding this comment.
I'm skeptical that another 30-day review/waiting period is needed. The original doc was presented at the Dash Forum awhile back and has been public for several months already. Let's just move forward.
There was a problem hiding this comment.
The 30 day audit period is part of every quarterly cycle. We presented the proposal and did a Dah Forum, yes, but have not yet notified contributors what roles they will have on the ladder (or off it). I have created a lot of scripts and tooling to capture contribution data, but it is also really important for contributors to have this period of time to share contributions they have made that cannot be captured in a script, like reproducing and verifying issues or coaching other contributors. This 30 notice period has always been included in the proposal for every audit cycle.
There was a problem hiding this comment.
Got it. I think I'm confused by the text a bit. It says "review window", so I thought that meant a review window for this RFC before we'd even start. But the "review window" here is the same as the grace period mentioned earlier in the proposal, is that right?
There was a problem hiding this comment.
Yes, good catch. I can definitely clear that up
Piinks
added
the
assign-rfc-number
github-actions
Bot
added
rfc-assigned
|
Assigned RFC 740.0001. |
So fancy |
Replaces and updates the original design document as a new RFC, now with implementation details.
Tracking issue: flutter/flutter#186415
Pre-launch Checklist
design doc.dart run bin/assign_rfc_number.dartlocally when instructed).If you need help, consider asking for advice on the #hackers channel on Discord.