From: Mike Gerwitz <mtg@gnu.org>
To: joinlaw <joinlaw@cock.li>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Electron replacement?
Date: Sun, 03 Feb 2019 09:28:09 -0500 [thread overview]
Message-ID: <871s4pc5fq.fsf@gnu.org> (raw)
In-Reply-To: 855fc19c-ec3a-b7d0-c33d-a99fcdfa1254@cock.li
[-- Attachment #1.1: Type: text/plain, Size: 1191 bytes --]
On Sun, Feb 03, 2019 at 14:30:37 +0300, joinlaw wrote:
> is there any libre replacement for electron js which is removed from parabola repos,
> electron uses Chromium as it's rendering engine and node.js, electron is
> used by many free software projects such as jitsi meet desktop client,
> riot.im desktop client, and draw.io and many others.
This implies that Electron is non-free. Is the concern over certain
unclear licensing practices of Chromium? If so, can Chromium just be
built without those unclearly-licensed components?
For example:
https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00009.html
If there is no intentional malice with regards to licensing from
Electron, Chromium, or any other projects involved, then it seems more
appropriate to me to fix or work around the issue than it does to avoid
the projects entirely. These are popular projects and it's in our best
interest to do our best to resolve the issues rather than sidestep them,
because they are not going away.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2019-02-03 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 11:30 Electron replacement? joinlaw
2019-02-03 14:28 ` Mike Gerwitz [this message]
2019-02-04 2:47 ` bill-auger
2019-02-09 17:21 ` joinlaw
2019-02-04 2:43 ` bill-auger
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s4pc5fq.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=joinlaw@cock.li \
--cc=libreplanet-discuss@libreplanet.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 read-only IMAP folder(s) and NNTP newsgroup(s).