all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 54267@debbugs.gnu.org
Subject: [bug#54267] [PATCH] doc: Add "Running Guix System on a Capsul Server" chapter.
Date: Mon, 7 Mar 2022 12:04:42 -0500	[thread overview]
Message-ID: <20220307120442.GB7531@gac.attlocal.net> (raw)
In-Reply-To: <a79391fd00ae5f4001f38c39612436e9653815c1.camel@ist.tugraz.at>

On Mon, 07 Mar 2022 13:28:58 +0100 Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> wrote:
> Sounds more like an ad than a recipe to me.  Note that "latest stable"
> means "I enjoy being part of a crypto-mining botnet and would like to
> dedicate more harware towards reaching the 3 degree target" when
> speaking about rolling release distribution models.  
> Then again... "cryptocurrency payments are back"[1].

I'd be less suspicious to promote Cyberia, a 501(c)(3) non-profit
organization providing the general public with Guix System virtual
private servers than DigitalOcean. Capsul's approach to providing Guix
System is a better approach than using some cloud infrastructure provider
that doesn't care to make Guix System a first-class citizen. I think we
should promote grassroots organizations like this and be more suspicious
of companies funded by VC money instead (DigitalOcean, Github, etc...).

all best,

jgart





  reply	other threads:[~2022-03-07 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06  3:28 [bug#54267] [PATCH] doc: Add "Running Guix System on a Capsul Server" chapter jgart via Guix-patches via
2022-03-07 12:28 ` Liliana Marie Prikler
2022-03-07 17:04   ` jgart via Guix-patches via [this message]
2022-03-09  8:36     ` Liliana Marie Prikler
2022-03-09 10:26       ` Maxime Devos
2022-07-07 20:21         ` bug#54267: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220307120442.GB7531@gac.attlocal.net \
    --to=guix-patches@gnu.org \
    --cc=54267@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=liliana.prikler@ist.tugraz.at \
    /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.