# Contributors Meetup Async Update - September 2nd, 2023 - September 15th, 2023 **URL:** \ **Category:** Core Contributors\ **Tags:** core-sprints, retrospective\ **Created:** [September 15, 2023, 7:22pm UTC](https://discuss.openedx.org/t/contributors-meetup-async-update-september-2nd-2023-september-15th-2023/11185 "2023-09-15T19:22:10Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![antoviaque](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/antoviaque/32/32_2.png) [@antoviaque](https://discuss.openedx.org/u/antoviaque)\ **Post date:** [September 21, 2023, 6:08pm UTC](https://discuss.openedx.org/t/contributors-meetup-async-update-september-2nd-2023-september-15th-2023/11185/3 "2023-09-21T18:08:14Z")
@Dean @Natalia_Choconta Thank you for the reports! 👍 > [@Natalia\_Choconta](#): > > Identify MFEs and new repos earlier and review the processes for enabling them. Advocate for better documentation and easier configuration while there’s still time to make changes. @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: > [@Peter Pinch](#): > > Not a new comment, but code contributors are still not familiar with the guidelines for annotating new settings (OEP-17). In this sprint, I just [commented on another PR that was missing annotations](https://github.com/mitodl/edx-sga/pull/344#discussion_r1325991232) 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](#): > > Still need someone with merge rights on opaque-keys to approve [fix: type hints weren’t installed properly, add type hints for Django Fields by bradenmacdonald · Pull Request #259 · openedx/opaque-keys · GitHub](https://github.com/openedx/opaque-keys/pull/259) @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](https://github.com/openedx/opaque-keys/pull/259#issuecomment-1730039737) > [@Peter Pinch](#): > > The gradebook MFE is broken (in master). We were able to fix it for our deployment by cherry-picking this open PR: [fix: replace Field.Email reference for Field.Text by dcoa · Pull Request #345 · openedx/frontend-app-gradebook · GitHub](https://github.com/openedx/frontend-app-gradebook/pull/345) Are there any core contributors with write permission on frontend-app-gradebook who could review? > We need a review of this frontend-app-learner-dashboard PR that fixes a branding issue: [fix: get brand logo file path from env by shahbaz-shabbir05 · Pull Request #205 · openedx/frontend-app-learner-dashboard · GitHub](https://github.com/openedx/frontend-app-learner-dashboard/pull/205) (this will be necessary before we default this MFE to be on in the next release) @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](https://github.com/openedx/frontend-app-gradebook/graphs/contributors) I also notice that @kmccormick has some commits on it - maybe you can help? CC @arbrandes too since this is frontend. > [@Pierre Mailhot](#): > > I cannot figure out what is the source of the problem in [[ECOM \> Create a course seat] \> After creating course I am not able to open its detail page · Issue #301 · openedx/wg-build-test-release · GitHub](https://github.com/openedx/wg-build-test-release/issues/301) > I can reproduce the problem, but the COURSE\_ID\_REGEX seems to validate the course session ending with 2000.02. @sambapete I see that you have been able to make progress on this, and got help from @regis - great! 👍 --- _[View the full topic](https://discuss.openedx.org/t/contributors-meetup-async-update-september-2nd-2023-september-15th-2023/11185)._