Repository navigation
Replies: 1 comment
|
@ump45nose, your 22 merged PRs comfortably meet the contribution threshold in FND-003 §5.1. I'm happy to recognize you as a Tier 2 Contributor. Your provider and channel fixes are a useful basis for taking on more review work. For a concrete next step, pick a provider or channel regression PR you didn't author, review it, and link your assessment here. Focus on whether it fixes the reported failure, what existing behavior it could break, and whether the tests establish the result. I'll review your assessment and compare notes with you. Non-required reviews are part of the Tier 2 path, so you can start there now. For a scoped maintainer role, I'd look for sustained judgment on other people's changes, useful issue triage, and follow-through when a fix needs revision. More merged PRs alone aren't the missing evidence. Core Team admission requires an explicit team decision, but this gives you a concrete way to build the review record for that discussion. |
Uh oh!
There was an error while loading. Please reload this page.
I've had 22 PRs merged since August, including OpenRouter streaming extras (#9782), interruption-scope isolation (#10958), approved shell reruns (#11653), and Telegram retry-after handling (#11650).
I'd like to be considered for a more involved contributor role around provider and channel regressions. FND-003 §5.1 describes Tier 2 recognition after two merged PRs, with non-required review participation; could the team confirm the appropriate recognition and reviewer path for my contributions?
I understand that Core Team membership is by invitation and a separate team decision. What additional review or triage evidence would you want to see before considering me for a scoped maintainer role?
All reactions