From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 32715@debbugs.gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: bug#32715: Chromium: scrolling doesn't work after a certain amount of time
Date: Sat, 29 Sep 2018 18:43:30 +0200 [thread overview]
Message-ID: <87va6ow8y5.fsf@gnu.org> (raw)
In-Reply-To: <20180929144254.GA16169@jasmine.lan> (Leo Famulari's message of "Sat, 29 Sep 2018 10:42:54 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Sep 29, 2018 at 03:54:23PM +0200, Clément Lassieur wrote:
>> PS: I'm unsure whether it makes sense to report bug for softwares that
>> are considered non-free and are just packaged in channels. If it
>> doesn't, I'll happily close my bugs reports.
>
> We don't use our official communication channels (the mailing lists and
> #guix IRC channel) to recommend non-free software. But Chromium is
> widely distributed under a BSD license, so I think we should consider it
> free. Guix goes beyond software freedom by following the FSDG [0], and
> the Chromium varant being discussed is specifically intended to comply
> with the FSDG.
>
> In general, we don't need to handle bug reports for packages in external
> channels. In this case, we are working to bring the package into GNU
> Guix, so it's appropriate to report issues here, in my opinion.
Agreed on all points.
Ludo’.
next prev parent reply other threads:[~2018-09-29 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 7:14 bug#32715: Chromium: scrolling doesn't work after a certain amount of time Clément Lassieur
2018-09-12 7:22 ` Clément Lassieur
2018-09-17 13:35 ` Marius Bakke
2018-09-29 13:54 ` Clément Lassieur
2018-09-29 14:42 ` Leo Famulari
2018-09-29 14:45 ` Clément Lassieur
2018-09-29 16:43 ` Ludovic Courtès [this message]
2019-02-19 7:57 ` Leo Famulari
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=87va6ow8y5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32715@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=leo@famulari.name \
/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).