From: "Thompson, David" <dthompson2@worcester.edu>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Why is it acceptable to have digital-ocean-configuration in the Guix?
Date: Thu, 4 Jan 2024 14:22:48 -0500 [thread overview]
Message-ID: <CAJ=Rwfa9ORVWhOWNz8-nVxsFLFdS-q+2z2YDCLUX8aO8X+W5Kg@mail.gmail.com> (raw)
In-Reply-To: <ZZaJlb2uEZSjG7Rk@ws>
On Thu, Jan 4, 2024 at 5:34 AM Tomas Volf <~@wolfsden.cz> wrote:
>
> Greetings,
>
> I would like to inquire regarding digital-ocean-configuration type used for
> provisioning DigitalOcean Droplets. I do not understand why it is acceptable to
> have this type in the source code. Reading the Free GNU/Linux distributions
> criteria[0] I see this sentence (emphasis mine):
>
> > This means they will include, and *propose*, exclusively free software.
>
> As far as I know DigitalOcean Droplets are not free software (please correct me
> if I am wrong). I contemplated on this for a bit, and I do not understand why
> it is acceptable.
>
> Would someone be so kind to explain the reason to me?
Perhaps this will help explain why you can't simply call a web service
nonfree: https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.en.html
To use a different example: Google doesn't publish the source code for
YouTube. Guix includes the free software yt-dlp program that can talk
to YouTube and download videos. Would you consider this a violation of
the FSDG?
Guix also downloads a lot of source code from GitHub. Is this an issue?
- Dave
next prev parent reply other threads:[~2024-01-04 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 10:33 Why is it acceptable to have digital-ocean-configuration in the Guix? Tomas Volf
2024-01-04 19:22 ` Thompson, David [this message]
2024-01-04 21:00 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-05 13:14 ` Tomas Volf
2024-01-09 22:53 ` Ludovic Courtès
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='CAJ=Rwfa9ORVWhOWNz8-nVxsFLFdS-q+2z2YDCLUX8aO8X+W5Kg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--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 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).