From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel@gnu.org, phodina@protonmail.com, ludo@gnu.org
Subject: Re: 04/04: gnu: Add fwupd.
Date: Wed, 31 Aug 2022 16:58:52 +0200 [thread overview]
Message-ID: <c1b8000610920cbc33c368da257737423fda704b.camel@gmail.com> (raw)
In-Reply-To: <87h71sa6iq.fsf@gmail.com>
Am Mittwoch, dem 31.08.2022 um 09:26 -0400 schrieb Maxim Cournoyer:
> Hi,
>
> guix-commits@gnu.org writes:
>
> > civodul pushed a commit to branch master
> > in repository guix.
> >
> > commit 23152ff70f0ed4966d8207846f54c793d7cb4f86
> > Author: Petr Hodina <phodina@protonmail.com>
> > AuthorDate: Tue Jan 4 06:58:51 2022 +0100
> >
> > gnu: Add fwupd.
> >
> > * gnu/packages/firmware.scm (fwupd): New variable.
> >
> > Signed-off-by: Ludovic Courtès <ludo@gnu.org>
>
> Just a quick question: does this tool talks to a remote server that
> serves non-free software as well as free one? If so, it'd need to be
> patched to comply with the FSDG.
I'd be surprised if it supplied free software as well as non-free one.
The vendor guide[1] states the following:
> Do I have to contribute any code?
>
> No, unless you're using a custom update protocol that fwupd does not
> already support.
The user guide[2] likewise states:
> The OEM vendor is in full control over what models are supported and is
> the only entity that can add support for new hardware.
The vendor agreement[3] further grants no freedom safe for the second –
the freedom to make unmodified copies.
Cheers
[1] https://fwupd.org/lvfs/docs/vendors
[2] https://fwupd.org/lvfs/docs/users
[3] https://fwupd.org/lvfs/docs/agreement
next prev parent reply other threads:[~2022-08-31 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166194391661.31756.9547474130907902222@vcs2.savannah.gnu.org>
[not found] ` <20220831110517.76C23C04F0B@vcs2.savannah.gnu.org>
2022-08-31 13:26 ` 04/04: gnu: Add fwupd Maxim Cournoyer
2022-08-31 14:58 ` Liliana Marie Prikler [this message]
2022-09-01 6:27 ` Reza Housseini
2022-09-01 7:03 ` Maxime Devos
2022-09-01 7:44 ` phodina
2022-09-01 13:42 ` Denis 'GNUtoo' Carikli
2022-09-01 20:35 ` Maxim Cournoyer
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=c1b8000610920cbc33c368da257737423fda704b.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=phodina@protonmail.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.
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).