...
Pylint amnesty +2
An open OEP we have on this:https://github.com/edx/open-edx-proposals/pull/108
Legacy FedX in LMS, Studio, etc. +1
We’re going to test
blackin our repos +2Conventions around commit messages / PR message content +3
A past attempt at this: https://github.com/edx/open-edx-proposals/pull/121
Potentially useful: https://github.com/marketplace/actions/issue-pull-request-body-regex-validator
JJ’s previous company found usefulness and success in having a shared convention for PR descriptions and commit messages.
Helped keeping a clean codebase, code archaeology, etc.
(Not sure if relevant): Browser extensions are required to go through Vendor Review process, including free ones - is this widely known/followed? What extensions are pre-approved/known to be ok?
Turns out this was a misunderstanding - there is no actual policy around browser extensions but to reach out & ask IT if you’re not sure about an extension or not (convo here: https://edx-internal.slack.com/archives/CDHMHCXC5/p1591903243463800)
How do people test with spoofed locations (e.g. you want to view content from Japan)?
You can apparently set the lat/long on newer versions of Chrome, but unclear how this works / how reliable it is (e.g. would CloudFlare recognize that your browser was “coming from Japan”?)