From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] albert 0.14.22 and later is both non-free (source-available) and copyright-infringing
Date: Mon, 01 Feb 2021 20:12:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28394@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
New issue by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/issues/28394
Description:
https://github.com/albertlauncher/albert/commit/18018c8f7b7dbbc366420c24ba1209bbda1f5267 removed the GPL license. New terms are, apparently,
> I explicitly allow packagers for linux distributions to package and distribute this software (note this applies only for the core app and library since the plugins may have their own licenses) if their distribution is avalailable free (no cost) for everybody. Modifications/patches have to come back upstream. You must not distribute a modified version of this software. Rationale is that I dont want users to run other peoples code in my name, i.e. protect users in a sense that they can check upstream to see what they get. Further this also avoids the potentially malicious ppas.
Unfortunately, a fair amount of code in the software was contributed by other people, under the original GPL terms, and cannot be included in a non-GPL work.
Ref:
https://bugs.archlinux.org/task/69366
https://github.com/albertlauncher/albert/issues/765#issuecomment-771086409
Recommendation:
Drop it like a hot potato.
(Alternatively, downgrade it and freeze it to an old version.)
next reply other threads:[~2021-02-01 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 19:12 eli-schwartz [this message]
2021-02-01 19:15 ` ericonr
2021-02-01 19:16 ` ericonr
2021-02-01 22:51 ` [ISSUE] [CLOSED] " Johnnynator
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28394@inbox.vuxu.org \
--to=eli-schwartz@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).