As we merge flutter/engine and flutter/flutter, we'll likely need to rethink our various "build health" rotations (i.e. Flutter Engine Sheriff, Flutter Tree Gardener), not immediately perhaps, but soon (TM), as there will be a single source of build and build health issues instead of split across two trees/repositories.

Here are some ideas in the back of my head, I'd be happy to be involved or help organize:

• Formal hand-off doc that is updated at least once a week (as rotations change) with what happened
• One merged rotation with a primary and a secondary (instead of two rotations with only a primary)
• More clear guidance on how time is expected to be spent during the rotation (i.e. little/no core work)
• More clear guidance on working hours/core hours (if someone helps fix the tree at 2am PST but is unavailable at 10am PST it sort of defeats the purpose of the rotation)