From: Ricardo Wurmus <rekado@elephly.net>
To: Mason Hock <mason@masonhock.com>
Cc: help-guix@gnu.org
Subject: Re: ungoogled-chromium
Date: Sat, 20 Apr 2019 09:27:35 +0200 [thread overview]
Message-ID: <87v9z9kufs.fsf@elephly.net> (raw)
In-Reply-To: <20190419221910.ltriqe5koweyoqvc@masonhock.com>
Hi Mason,
> I see that ungoogled-chromium is included in the guix repo. I was
> wondering if you were aware of these licensing issues[1] in Chromium and
> have determined that they are either not a FSDG issue or not present in
> ungoogled-chromium.
This topic has been discussed multiple times on this list and the GNU
list for libre systems, so yes, we are aware of licensing issues in
Chromium itself, and remaining issues in ungoogled chromium were
investigated as well.
--
Ricardo
next prev parent reply other threads:[~2019-04-20 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 22:19 ungoogled-chromium Mason Hock
2019-04-20 0:54 ` ungoogled-chromium beoram
2019-04-20 7:27 ` Ricardo Wurmus [this message]
2019-04-20 18:12 ` ungoogled-chromium Mason Hock
2019-04-20 19:59 ` ungoogled-chromium Julien Lepiller
2019-04-20 20:10 ` ungoogled-chromium Mason Hock
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 12:02 ungoogled-chromium Marco van Hulten
2020-03-22 12:31 ` ungoogled-chromium Marius Bakke
2020-03-22 12:37 ` ungoogled-chromium Ricardo Wurmus
2020-03-22 12:58 ` ungoogled-chromium Marco van Hulten
2020-03-22 13:14 ` ungoogled-chromium Vagrant Cascadian
2020-03-22 14:16 ` ungoogled-chromium Marius Bakke
2020-03-22 16:18 ` ungoogled-chromium Marco van Hulten
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9z9kufs.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mason@masonhock.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.
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).