From: mikadoZero <mikadozero@yandex.com>
To: guix-devel@gnu.org
Subject: Re: CDN Test Results - Should We Continue Using a CDN?
Date: Mon, 11 Mar 2019 15:25:13 -0400 [thread overview]
Message-ID: <o96htdra.fsf@yandex.com> (raw)
In-Reply-To: <87imwptmql.fsf@elephly.net>
Thank you for correcting my false assumptions and sharing that link.
Ricardo Wurmus writes:
> mikadoZero <mikadozero@yandex.com> writes:
>
>> In "14.4.1 Software Freedom" of the Guix manual it says that Guix is free
>> software and follows the free software distribution guidelines.
>>
>> Is using a proprietary non free CDN as a core part of Guix's
>> infrastructure in conflict with Guix's software freedom?
>
> Two things:
>
> 1) It is not a core part of Guix’s infrastructure. People who want to
> bypass the CDN can do so by fetching substitutes from berlin.guixsd.org
> instead of ci.guix.info. People can also opt out of getting substitutes
> all together or choose to get them from some other build farm. (The
> build farm is little more than another Guix user.)
>
> 2) “proprietary” / “non-free” terminology does not apply to services.
> See also
> https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html
>
> This is a case of “Service as a Hardware Substitute” where we pay to use
> hardware that we do not physically control to substitute for having to
> own and maintain hardware at a large number of physical locations in the
> world.
>
>> Using a proprietary CDN has the potential for an unplanned increase in
>> workload. This is because of the combination of vendor lock in and
>> product line discontinuation. Which could create unplanned rework of
>> setting up a CDN elsewhere. This hinders Guix's resource planning by
>> introducing the potential for surprise rework.
>
> There is no vendor lock in. We can drop and have dropped the use of a
> CDN without service interruption. If the CDN service were to be
> discontinued we would simply revert to not offering package distribution
> via CDN.
next prev parent reply other threads:[~2019-03-11 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 3:47 CDN Test Results - Should We Continue Using a CDN? Chris Marusich
2019-03-11 8:09 ` Pierre Neidhardt
2019-03-11 15:16 ` mikadoZero
2019-03-11 16:11 ` Ricardo Wurmus
2019-03-11 19:25 ` mikadoZero [this message]
2019-03-12 0:57 ` Maxim Cournoyer
2019-03-12 3:21 ` Chris Marusich
2019-03-12 13:38 ` Ludovic Courtès
2019-03-13 2:13 ` Maxim Cournoyer
2019-03-14 20:12 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=o96htdra.fsf@yandex.com \
--to=mikadozero@yandex.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.