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

[josef.pktd at gmail.com]

BSD-3 compatible licensed is preferred from a developer perspective because
then we can also freely look at each others code, and possibly copy code or
move parts into scipy.

However, some packages are GPL because of a requirement from the underlying
code. For example, scikit-sparse uses CHOLMOD which I would like to use
from scipy, but it is GPL and would "infect" scipy's license if used/copied
there.
Some packages that are overall GPL because of some included code, but have
additionally a more permissible license on parts of the code if that code
is reused without the GPL part.

Josef


On Thu, Aug 9, 2018 at 8:54 AM, Sylvain Corlay <sylvain.corlay at gmail.com>
wrote:

> Arg too bad :)
>
> I guess that you are stuck with gpl unless all the copyright holders agree
> to change it...
>
> On Thu, Aug 9, 2018, 14:48 Magnus Nord <magnunor at gmail.com> wrote:
>
>> The reason for having this new library be GPLv3 is that HyperSpy itself
>> is GPLv3, and most of the code will simply be copy-pasted from HyperSpy's
>> IO-module into the new library.
>>
>> Magnus
>>
>> On 08/09/2018 02:31 PM, Sylvain Corlay wrote:
>>
>> Their recommendation is BSD although they are ok with other OSI-approved
>> licenses.
>>
>> I think that using the scikit prefix for GPL software breaks people's
>> expectations about the python scientific stack and is therefore misleading
>> but it is only my opinion.
>>
>> Was the choice of GPLv3 over BSD deliberate or just a stab in the dark?
>>
>> On Thu, Aug 9, 2018, 11:41 Magnus Nord <magnunor at gmail.com> wrote:
>>
>>> The scikit "label" is indeed fairly permissive. Taken from the Scipy's
>>> scikit page (https://www.scipy.org/scikits.html):
>>>
>>>    - The package is deemed too specialized to live in SciPy itself or
>>>    - The package has a GPL (or similar) license which is incompatible
>>>    with SciPy’s BSD license or
>>>    - The package is meant to be included in SciPy, but development is
>>>    still in progress.
>>>
>>> So using GPLv3 should be in line with the scikit prefix intentions?
>>>
>>> Magnus
>>>
>>> On 08/09/2018 09:52 AM, Sylvain Corlay wrote:
>>>
>>> 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
>>>>
>>>
>>>
>>> _______________________________________________
>>> SciPy-Dev mailing listSciPy-Dev at python.orghttps://mail.python.org/mailman/listinfo/scipy-dev
>>>
>>>
>>> _______________________________________________
>>> SciPy-Dev mailing list
>>> SciPy-Dev at python.org
>>> https://mail.python.org/mailman/listinfo/scipy-dev
>>>
>>
>>
>> _______________________________________________
>> SciPy-Dev mailing listSciPy-Dev at python.orghttps://mail.python.org/mailman/listinfo/scipy-dev
>>
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
>
> _______________________________________________
> 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/54cdca54/attachment.html>