From: Jean Louis <bugs@gnu.support>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Boruch Baum <boruch_baum@gmx.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: non-gnu elpa issue tracking
Date: Thu, 10 Dec 2020 02:40:40 +0300 [thread overview]
Message-ID: <X9FgeLr13DocrONY@protected.rcdrun.com> (raw)
In-Reply-To: <CADwFkmkBso6QA3NNf=fYYp9TeEhJC0gaHd2Faa4Nyi90EBgzfg@mail.gmail.com>
* Stefan Kangas <stefankangas@gmail.com> [2020-12-10 00:48]:
> Jean Louis <bugs@gnu.support> writes:
>
> >> Are there any packages out there that don't use the GPL? Could you
> >> point us to some examples?
> >
> > Just to name a few, among more of them:
>
> Thanks for the list.
>
> > anki-mode-20200703.739.el
> > - no license, proprietary by default
>
> It seems to be under the GPL:
>
> https://github.com/davidshepherd7/anki-mode/blob/master/LICENCE
Not that I am personally asking. Please think of conveying software
and end user receiving software without license. If it is received
without license software is proprietary for the end user.
Software can be double licensed and be "same" inside. If there is no
license distributed with the software together a receiver cannot just
stumble upon some license on Internet and assume to put it
together. Then the repository is not verified to be author's
repository, it could be fork and licenses could be added there. For
GNU ELPA is good to verify apparently dubious packages if they are
licensed or not, and that they are sourced from their authors. There
are many problems related to licensing specifically on Github:
https://github.com/github/dmca/search?q=GPL&type=
> MELPA requires a "GPL compatible license", according to
>
> https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org
>
> so I guess the "proprietary by default" packages you are speaking of are
> simply missing the license information in the library itself? Sounds
> like that should be reported as a bug against those packages.
Who am I to decide? If fetch a package from MELPA git repository and
there is no license in the file, it is proprietary for me. As simple
as that. Ask attorneys in the FSF if my statements do not make sense
but you still think there could be something.
Your software you may give to person Joe without license rendering it
proprietary for Joe. And you may give it to Jane under free software
license. Joe cannot ask Jane to give him a license to make it
free. Legal world does not work that way as he did not receive the
license from the author or other person licensed to convey software
and license to new receiver.
> PS. I've opened a pull request against anki-mode to add the license
> header.
Good if that package is destined for the non GNU ELPA, but if not
destined, then doing reports for licenses should be made by priorities
for those packages that developers want to have in non GNU ELPA.
Jean
next prev parent reply other threads:[~2020-12-09 23:40 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 12:55 non-gnu elpa issue tracking Boruch Baum
2020-12-09 16:58 ` Stefan Kangas
2020-12-09 19:18 ` Jean Louis
2020-12-09 21:48 ` Stefan Kangas
2020-12-09 23:40 ` Jean Louis [this message]
2020-12-09 23:58 ` Jean Louis
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:05 ` Richard Stallman
2020-12-10 4:32 ` Richard Stallman
2020-12-10 6:28 ` Jean Louis
2020-12-09 19:23 ` Jean Louis
2020-12-09 23:22 ` Thibaut Verron
2020-12-10 0:09 ` Jean Louis
2020-12-10 9:14 ` Thibaut Verron
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:19 ` Thibaut Verron
2020-12-10 16:37 ` Jean Louis
2020-12-11 6:10 ` Richard Stallman
2020-12-10 11:49 ` Jean Louis
2020-12-10 14:05 ` Stefan Kangas
2020-12-10 15:48 ` Stefan Monnier
2020-12-10 16:05 ` Jean Louis
2020-12-10 17:35 ` Stefan Monnier
2020-12-11 6:09 ` Richard Stallman
2020-12-11 6:04 ` Richard Stallman
2020-12-11 11:10 ` Thibaut Verron
2020-12-12 5:34 ` Richard Stallman
2020-12-12 6:37 ` Tim Cross
2020-12-12 10:08 ` Thibaut Verron
2020-12-12 15:23 ` Tim Cross
2020-12-12 17:07 ` Thibaut Verron
2020-12-13 4:56 ` Richard Stallman
2020-12-13 5:20 ` Tim Cross
2020-12-13 9:54 ` Andrea Corallo via Emacs development discussions.
2020-12-13 22:59 ` Tim Cross
2020-12-14 0:32 ` Stefan Monnier
2020-12-14 0:54 ` Tim Cross
2020-12-14 4:36 ` Stefan Monnier
2020-12-14 5:45 ` Tim Cross
2020-12-15 5:44 ` Richard Stallman
2020-12-14 10:03 ` Alfred M. Szmidt
2020-12-14 14:57 ` Stefan Monnier
2020-12-14 15:01 ` Alfred M. Szmidt
2020-12-14 15:12 ` Stefan Monnier
2020-12-14 15:52 ` Eli Zaretskii
2020-12-14 0:16 ` Stephen Leake
2020-12-13 4:56 ` Richard Stallman
2020-12-13 8:56 ` Vasilij Schneidermann
2020-12-14 5:50 ` Richard Stallman
2020-12-14 6:45 ` Jean Louis
2020-12-12 13:48 ` Michael Albinus
2020-12-12 13:50 ` Stefan Monnier
2020-12-12 15:37 ` Tim Cross
2020-12-12 19:54 ` Jean Louis
2020-12-12 20:46 ` Stephen Leake
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-12 21:48 ` Christopher Dimech
2020-12-13 0:39 ` Tim Cross
2020-12-13 1:28 ` Christopher Dimech
2020-12-13 5:03 ` Richard Stallman
2020-12-13 4:58 ` Richard Stallman
2020-12-12 21:06 ` Dmitry Gutov
2020-12-13 4:58 ` Richard Stallman
2020-12-13 5:27 ` Christopher Dimech
2020-12-12 19:33 ` Jean Louis
2020-12-12 21:24 ` Alfred M. Szmidt
2020-12-13 4:59 ` Richard Stallman
2020-12-13 5:03 ` Richard Stallman
2020-12-14 17:38 ` Jean Louis
2020-12-14 18:49 ` Vasilij Schneidermann
2020-12-14 22:13 ` Jean Louis
2020-12-14 19:10 ` Boruch Baum
2020-12-14 22:17 ` Jean Louis
2020-12-16 5:32 ` Richard Stallman
2021-01-02 5:25 ` Richard Stallman
2020-12-10 4:35 ` Richard Stallman
2020-12-10 5:03 ` Boruch Baum
2020-12-10 5:55 ` Eli Zaretskii
2020-12-10 6:39 ` "Open records", "good government principles", "corporate culture" Boruch Baum
2020-12-10 7:27 ` Jean Louis
2020-12-10 14:08 ` Eli Zaretskii
2020-12-11 6:16 ` Richard Stallman
2020-12-10 6:54 ` non-gnu elpa issue tracking Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9FgeLr13DocrONY@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).