[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: non-gnu elpa issue tracking
From: |
Jean Louis |
Subject: |
Re: non-gnu elpa issue tracking |
Date: |
Mon, 14 Dec 2020 06:45:15 +0000 |
On that I did not look into original packages, but only those distributed by
Melpa and I do think that many without license on Melpa have their license
somewhere.
It does not change the condition that distributing packages without license is
license violations, and that nonGnu ELPA has to do it better without comparing
to Melpa.
On December 13, 2020 8:56:09 AM UTC, Vasilij Schneidermann <mail@vasilij.de>
wrote:
>> If someone is willing to focus on organizing this effort, it might do
>> some good. One very good step would be to convince GitHub to
>identify
>> packages with the modern SPDX identifiers.
>
>GitHub does already try to recognize the license used by a repository
>using heuristics. These can be programmatically fetched:
>
> $ curl --silent -H 'Accept: application/vnd.github.v3+json' \
> https://api.github.com/repos/melpa/melpa/license | grep spdx
> "spdx_id": "GPL-3.0",
>
>Repeating this process for some packages mentioned previously in this
>discussion (the 0x0 one has been omitted as it's hosted on sr.ht):
>
> $ curl --silent -H 'Accept: application/vnd.github.v3+json' \
>https://api.github.com/repos/davidshepherd7/aggressive-fill-paragraph-mode/license
>| grep spdx
> "spdx_id": "GPL-3.0",
> $ curl --silent -H 'Accept: application/vnd.github.v3+json' \
>https://api.github.com/repos/alan-platform/AlanForEmacs/license | grep
>spdx
> "spdx_id": "MIT",
> $ curl --silent -H 'Accept: application/vnd.github.v3+json' \
> https://api.github.com/repos/rolandwalker/anaphora/license | grep spdx
> $ curl --silent -H 'Accept: application/vnd.github.v3+json' \
>https://api.github.com/repos/davidshepherd7/anki-mode/license | grep
>spdx
> "spdx_id": "AGPL-3.0",
>
>That gives me a more precise picture than Jean Louis' analysis I've
>taken these packages from. The only license that couldn't be identified
>is for the anaphora repository which doesn't have a LICENSE file, but
>instead embeds a public domain notice inside the source code.
Jean
- Re: non-gnu elpa issue tracking, (continued)
- Re: non-gnu elpa issue tracking, Richard Stallman, 2020/12/15
- Re: non-gnu elpa issue tracking, Alfred M. Szmidt, 2020/12/14
- Re: non-gnu elpa issue tracking, Stefan Monnier, 2020/12/14
- Re: non-gnu elpa issue tracking, Alfred M. Szmidt, 2020/12/14
- Re: non-gnu elpa issue tracking, Stefan Monnier, 2020/12/14
- Re: non-gnu elpa issue tracking, Eli Zaretskii, 2020/12/14
- Re: non-gnu elpa issue tracking, Stephen Leake, 2020/12/13
- Re: non-gnu elpa issue tracking, Richard Stallman, 2020/12/12
- Re: non-gnu elpa issue tracking, Vasilij Schneidermann, 2020/12/13
- Re: non-gnu elpa issue tracking, Richard Stallman, 2020/12/14
- Re: non-gnu elpa issue tracking,
Jean Louis <=
- Re: non-gnu elpa issue tracking, Stefan Monnier, 2020/12/12
- Re: non-gnu elpa issue tracking, Tim Cross, 2020/12/12
- Re: non-gnu elpa issue tracking, Jean Louis, 2020/12/12
- Re: non-gnu elpa issue tracking, Stephen Leake, 2020/12/12
- Re: non-gnu elpa issue tracking, Alfred M. Szmidt, 2020/12/12
- Re: non-gnu elpa issue tracking, Christopher Dimech, 2020/12/12
- Re: non-gnu elpa issue tracking, Tim Cross, 2020/12/12
- Re: non-gnu elpa issue tracking, Christopher Dimech, 2020/12/12
- Re: non-gnu elpa issue tracking, Richard Stallman, 2020/12/13
- Re: non-gnu elpa issue tracking, Richard Stallman, 2020/12/12