[SciPy-Dev] scikit prefix for microscopy file I/O library?

[Sylvain Corlay]

Hi Magnus,

I am not sure if anyone "owns" the scikit prefix.

Although I think that most people would expect a scikit-foobar to be BSD
licensed like scipy, scikit-learn, scikit-image, scikit-optimize etc. So I
would find it misleading for GPL-licensed software to adopt this naming
pattern.

Sylvain


On Thu, Aug 9, 2018, 09:11 Magnus Nord <magnunor at gmail.com> wrote:

> I'm one of the developers in the HyperSpy project, which is an open
> source python library for analysing multidimensional data, with a focus
> on electron microscopy. We're in the processes of splitting the project
> into smaller pieces, to i) make the code a bit more manageable, ii) make
> it easier for other projects to use specific functionalities without
> having to install a lot of extra dependencies.
>
> The current focus is moving the file reading/writing functionality to
> its own library, which includes readers for many types of proprietary
> electron microscopy file formats. The plan is to keep the GPLv3 license,
> and only depend on the more standard scientific python stack (numpy, ...).
>
> However, we've been having some issues in deciding on a name for the
> library, and someone suggested using a scikit- prefix
> (scikit-microscopyIO?, scikit-microscopy-io?). So I'm wondering if a
> scikit prefix would be appropriate for a library focused on file I/O of
> microscopy data?
>
> Discussion on this in the HyperSpy issue tracker:
> https://github.com/hyperspy/hyperspy/issues/1978
>
> Magnus
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180809/0a5915dc/attachment.html>