unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julie Marchant <onpon4@riseup.net>
To: "Workgroup for fully free GNU/Linux distributions"
	<gnu-linux-libre@nongnu.org>,
	"Christopher Lemmer Webber" <cwebber@dustycloud.org>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 28004@debbugs.gnu.org
Subject: Re: [PATCH] gnu: Add ungoogled-chromium.
Date: Thu, 7 Feb 2019 18:59:02 -0500	[thread overview]
Message-ID: <794ccf8b-cee1-5588-976f-085d37a0bc2a@riseup.net> (raw)
In-Reply-To: <87tvhf5f8d.fsf@dustycloud.org>

On 02/07/2019 06:52 PM, Christopher Lemmer Webber wrote:
> Ludovic Courtès writes:
> 
>> Hi bill-auger,
>>
>> bill-auger <bill-auger@peers.community> skribis:
>>
>>> re: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00009.html
>>>
>>> i would like to remind readers of the guix-devel list that it was
>>> discussed some months ago, why no FSDG distros currently distribute
>>> chromium[1] - it appeared at that time, that most people in that
>>> discussion were in agreement that chromium should not be included in
>>> guix; and marius was instead hosting it in a private repo, as not to
>>> taint the main guix repos with dubious software - has there been a
>>> notable break-through since then?
>>
>> It’s not entirely clear to me what the problems are, to be honest.
>> Marius listed specific issues that were addressed by the patches; others
>> then pointed out at additional issues that ungoogled-chromium fixes,
>> which Marius took into account; what’s left now?
>>
>> I understand you’re skeptical about Chromium, but we cannot base
>> decisions based on vague skepticism.  If you know of issues that are
>> still unaddressed, please do list them.
>>
>> I’d also like to stress that, if Chromium is eventually included in
>> Guix, we are committed to fixing it or removing it should someone later
>> discover that it does not comply with the FSDG (that’s the “Commitment
>> to Correct Mistakes” section of FSDG.)
> 
> +1 ... If concrete problems are found, by all means those should be
> raised and addressed.  Otherwise I really think we ought to merge this
> work.

Yes, exactly.

-- 
Julie Marchant
http://onpon4.github.io

Encrypt your emails with GnuPG:
https://emailselfdefense.fsf.org

  reply	other threads:[~2019-02-07 23:59 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y3qvb15k.fsf@fastmail.com>
2019-02-02 19:20 ` [PATCH] gnu: Add ungoogled-chromium Marius Bakke
2019-02-03 18:16   ` Joshua Branson
2019-02-04  4:52     ` bill-auger
2019-02-04  5:52       ` brettg
2019-02-04  7:46       ` Ineiev
2019-02-04 10:56         ` bill-auger
2019-02-04 14:43           ` Jean Louis
2019-02-04 12:26       ` [GNU-linux-libre] " Julie Marchant
2019-02-04 15:03         ` bill-auger
2019-02-04 22:34       ` Ludovic Courtès
2019-02-06 21:04         ` [GNU-linux-libre] " Marius Bakke
2019-02-07 23:52         ` Christopher Lemmer Webber
2019-02-07 23:59           ` Julie Marchant [this message]
2019-02-16  8:00           ` bill-auger
2019-02-16 10:25             ` Brett Gilio
2019-02-16 14:18               ` Julie Marchant
2019-02-16 15:37                 ` [GNU-linux-libre] " Adam Van Ymeren
2019-02-16 19:47                 ` Adonay Felipe Nogueira
2019-02-16 20:01                   ` Brett Gilio
2019-02-16 20:06                     ` Brett Gilio
2019-02-17  1:39                       ` bill-auger
2019-02-17 22:33                         ` [GNU-linux-libre] " Ricardo Wurmus
2019-02-18 12:05                           ` bill-auger
2019-02-18 12:15                             ` Hartmut Goebel
2019-02-18 13:44                             ` Tobias Geerinckx-Rice
2019-02-18 19:22                               ` Simon Nielsen
2019-02-19 20:45                                 ` [GNU-linux-libre] " bill-auger
2019-02-16 20:07                   ` Alex Griffin
2019-02-17  1:49                     ` bill-auger
2019-02-17  1:37                 ` bill-auger
2019-02-17  2:30                   ` Julie Marchant
2019-02-17  2:42                     ` bill-auger
2019-02-17  4:19                       ` Julie Marchant
2019-02-17  7:43                         ` bill-auger
2019-02-17 14:06                           ` Julie Marchant
2019-02-18  7:43                             ` bill-auger
2019-02-17 20:55                 ` Christopher Lemmer Webber
2019-02-16 11:16             ` Gábor Boskovits
2019-02-16 12:55               ` ng0
2019-02-16 13:10                 ` Gábor Boskovits
2019-02-18 13:47               ` Denis 'GNUtoo' Carikli
2019-02-16 15:10             ` znavko
2019-02-16 15:50             ` Marius Bakke
2019-02-16 16:20               ` [GNU-linux-libre] " Amin Bandali
2019-02-16 16:33                 ` Marius Bakke
2019-02-16 19:27                   ` Amin Bandali
2019-02-17  2:20                   ` bill-auger
2019-02-16 16:34               ` Alexandre Oliva
2019-02-16 16:54                 ` Marius Bakke
2019-02-17  3:38                 ` bill-auger
2019-02-16 18:56             ` Giovanni Biscuolo
2019-02-19 16:28               ` Giovanni Biscuolo
2019-02-09 14:04       ` Adonay Felipe Nogueira
2019-02-03 20:21   ` Amin Bandali
2019-02-05  5:22   ` [bug#28004] " swedebugia
2019-02-12 15:58   ` [PATCH v2] " Marius Bakke
2019-02-18 22:43     ` [bug#28004] " Marius Bakke

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=794ccf8b-cee1-5588-976f-085d37a0bc2a@riseup.net \
    --to=onpon4@riseup.net \
    --cc=28004@debbugs.gnu.org \
    --cc=cwebber@dustycloud.org \
    --cc=gnu-linux-libre@nongnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).