From: Chad Brown <yandros@gmail.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Grave ethical problem in MELPA
Date: Thu, 11 Aug 2016 22:27:02 -0700 [thread overview]
Message-ID: <F2C6B739-F97F-4027-A8E9-14563216B769@gmail.com> (raw)
In-Reply-To: <E1bY4Db-0004EG-Na@fencepost.gnu.org>
> On 11 Aug 2016, at 21:37, Richard Stallman <rms@gnu.org> wrote:
>
> I'm told that the MELPA site requires nonfree software:
>
>> The navigational buttons do nothing while the rest of what would
>> show on the homepage without LibreJS deactivated is absent.
>
> This is unethical and works directly against what we say. Does anyone
> here know the site maintainers well enough to convince them to fix
> this?
>
> Please respond if you can try.
The melpa site includes two links at the bottom of the page, one to the source of the page, and one to “Javascript license information”. The second one goes to:
http://melpa.org/jslicense.html
This page is totally viewable in eww, and all of the licenses on it seem to be compatible with the GPL according to:
https://www.gnu.org/licenses/license-list.en.html
That said, I imagine that there might be some troubles with LibreJS identifying javascript libraries correctly; I’ve heard comments that suggest that LibreJS is imperfect at this job so far.
I don’t use the melpa web site anymore myself, and I don’t have any particular connection to the maintainers there myself.
Hope this helps,
~Chad
next prev parent reply other threads:[~2016-08-12 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 4:37 Grave ethical problem in MELPA Richard Stallman
2016-08-12 5:27 ` Chad Brown [this message]
2016-08-12 5:36 ` Dmitry Gutov
2016-08-12 8:09 ` Uwe Brauer
2016-08-13 5:11 ` Richard Stallman
2016-08-12 13:22 ` LibreJS doesn't detect free software licenses with 100% accuracy (was: Grave ethical problem in MELPA) Clément Pit--Claudel
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=F2C6B739-F97F-4027-A8E9-14563216B769@gmail.com \
--to=yandros@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.