Taking on ongoing maintenance responsibilities

[DaoyuanLi2816]

Hi @qgallouedec,

I'd like to contribute beyond individual fixes and help with ongoing maintenance in TRL. My merged contributions include #6192 (ZeRO-3 + PEFT mixed-dtype fixes across trainers) and #6554 (avoiding CopySlices when scaling policy logits).

Would sustained help with issue reproduction, regression tests, or initial triage in a specific area of the currently supported trainers be useful? I'd prefer to focus on the team's current priorities rather than assume which area needs more work.

Is there a path for regular contributors to take on a triage or collaborator role, and what responsibilities or track record would you want to see first? I'm happy to start with a small, clearly scoped responsibility under the team's guidance.