Richard Tibbles

Thanks @Yashpreet-Singh-Jagdev, I will unassign you. Unfortunately, we are not currently hiring any software engineers at this time. If we openly advertise an opportunity, we will be sure to share...

See #203 for more historic context

Switching to draft - something has gone awry in the build that I hadn't seen previously.

Issues resolved.

> Or just that doing both feels unnecessary. It felt a little unnecessary, but also both are completely doable, and would help signpost it more, if you happened to be...

> I don't have a strong opinion on this, but I think for the sake of consistency, having it also in a /src package makes sense to me. In that...

> On the topic of public vs private, the exports field, and prefixing _ to explicitly distinguish private code, could using the _ convention allow us to write a linting...

> It appears this feature is also possible Interesting, so technically you could do a wild card instead of `feature` and have it so any folder labelled with `internal` is...

Added follow up issue for resolving the `src` folder work here: https://github.com/learningequality/kolibri/issues/12780

Ideas so far: Manual data capture: * Exporting HAR files from the network tab to understand network traffic when this happens. * Doing a memory profile to see what is...