@Dean @Natalia_Choconta Thank you for the reports! 
@jalondonot Maybe a solution to this would be to include someone from the BTR working groups in reviews of new repos & MFEs going forward? @itsjeyd Do we have a way to implement this for all PRs with our current processes? I’m guessing we currently only have a formal process for the OSPRs - but maybe we should have one for all PRs, to enable things like this?
Actually, another blocker reported by @pdpinch could also benefit from that:
We have talked about introducing a bot for helping to manage OSPRs - maybe it could help more broadly, by suggesting/pinging reviewers based on the code that’s being modified?
@braden Ah, you need a binding - I hadn’t realized that previously, I thought you only needed people to review and make comments. I’ve replied on the PR and pinged @itsjeyd for help: fix: type hints weren't installed properly, add type hints for Django Fields by bradenmacdonald · Pull Request #259 · openedx/opaque-keys · GitHub
@pdpinch I see that @Michelle_Philbrick is already on it, though it looks like we still don’t know who can review on this. Similarly to my comment above to Braden and @itsjeyd – do we have a way to tell who has commit rights and can give a binding on the repo? And @pdpinch any suggestions on who could be a good reviewer for the PR, even if they don’t have the rights yet? From Contributors to openedx/frontend-app-gradebook · GitHub I also notice that @kmccormick has some commits on it - maybe you can help? CC @arbrandes too since this is frontend.
@sambapete I see that you have been able to make progress on this, and got help from @regis - great!