Make public and release

[hawesie]

Hey @Pandoro please can you make this public and release it? Some of our other packages now depend on it, so it would be useful if we can now include this in the normal STRANDS release procedures.

[hawesie]

An alternative approach might be to separate the service definitions out to a releasable package and keep the implementation private.

[Pandoro]

If people are actually using this, I'm fine with releasing it. I just a have some issues about the licensing since I'm not really an expert on this and I just copy pasted the code form three projects who are all released with different licenses and partially contain even different external libraries. If anyone could give me some pointers here on how to handle this the best I'd be happy to release it. I'd be fine with an MIT license, I just guess I can't do that if I use other stuff not using the same license?

Furthermore the RF model is very specific for the STRANDS case and will completely fail if anyone just uses it with something else. I'm fine with releasing it as is, I'm just not really sure how to deal with the download from the random forest model file. Should this be handled during the installing of the package, e.g. in a setup file that downloads it?

[hawesie]

It's public.