From mboxrd@z Thu Jan 1 00:00:00 1970 From: mikadoZero Subject: Re: CDN Test Results - Should We Continue Using a CDN? Date: Mon, 11 Mar 2019 15:25:13 -0400 Message-ID: References: <87d0my1380.fsf@gmail.com> <87imwptmql.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:34199) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h3Qaa-000408-Dy for guix-devel@gnu.org; Mon, 11 Mar 2019 15:27:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h3QYN-0006iy-Hi for guix-devel@gnu.org; Mon, 11 Mar 2019 15:25:41 -0400 Received: from forward101j.mail.yandex.net ([2a02:6b8:0:801:2::101]:45918) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h3QYL-0006fv-QS for guix-devel@gnu.org; Mon, 11 Mar 2019 15:25:38 -0400 Received: from mxback1o.mail.yandex.net (mxback1o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::1b]) by forward101j.mail.yandex.net (Yandex) with ESMTP id 8F5531BE0A8A for ; Mon, 11 Mar 2019 22:25:30 +0300 (MSK) In-reply-to: <87imwptmql.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Thank you for correcting my false assumptions and sharing that link. Ricardo Wurmus writes: > mikadoZero 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=E2=80=99s infrastructure. People who wa= nt 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) =E2=80=9Cproprietary=E2=80=9D / =E2=80=9Cnon-free=E2=80=9D 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 =E2=80=9CService as a Hardware Substitute=E2=80=9D wher= e 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.