Dilum Aluthge

I agree. I think that, potentially, the precompilation cache (`~/.julia/compiled`) could go in the CACHE category. But I agree that packages and artifacts should probably not go into the CACHE...

We have some functionality in [ClassImbalance.jl](https://github.com/bcbi/ClassImbalance.jl), but there is not yet an MLJ interface for that package. Help is welcome.

Yeah the package needs to be updated and modernized.

Yeah shouldn't be too hard.

I'll work on it here: https://github.com/alan-turing-institute/MLJModels.jl/pull/369

> This curated list could be made a dependency of the umbrella package. I don't think users would complain about too many dependencies given that any modern ML pipeline nowadays...

> If the "umbrella package" is MLJ.jl, then I would definitely complain. I don't want `] add MLJ` to install the entire kitchen sink. For example, the ensemble functionality lives...

Now, on the other hand, if we first moved ALL of the functionality out of MLJ.jl into other repos, then I would have no problem adding a whole bunch of...

So I guess the two options are: 1. Keep MLJ.jl the way it is, and put the curated list in a separate MLJCuratedModels.jl package. 2. Move ALL of the actual...

This seems like a really important test to have. @KristofferC Do you have any ideas how we might implement this test?