unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion via <help-guix@gnu.org>
To: Yasuaki Kudo <yasu@yasuaki.com>, help-guix <help-guix@gnu.org>
Subject: Re: Enterprise Guix Hosting?
Date: Sat, 30 Jul 2022 10:36:10 -0400	[thread overview]
Message-ID: <874jyy3bxh.fsf@laura> (raw)
In-Reply-To: <E605A22B-D840-4A7A-91DD-764A8E573125@yasuaki.com>

On Sat, 30 Jul 2022, Yasuaki Kudo <yasu@yasuaki.com> wrote:
> I have been exposed to the world of Docker images and Continuous
> Integration that seem spend most of the time downloading and building
> them 😅

Yup.  Tons of energy wasted and pollution generated.

> Have you heard of Guix Hosting services jusy like the Docker or Github
> companies target enterprises customers?

IMO Guix is still very niche.  Only a handful of Unix enthusiasms /
scientifics use it and companies are not in yet.  I might be wrong.

> My partners and I are just starting an IT worker cooperative and I
> thought this might be an interesting thing to get into!

I think it is.  I know that some companies pay very good for support
related to dev-op, e.g. CI.  I think that Guix could fit very well for
professional services and software as a services.  However, Guix
probably needs to be more main stream for that to work.

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-07-30 14:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via [this message]
2022-07-30 16:20   ` Phil
2022-07-30 23:18     ` Yasuaki Kudo
2022-07-31  0:42       ` Benjamin Slade
2022-07-31 11:01         ` Phil
2022-08-09 20:37           ` Ludovic Courtès
2022-08-09 22:24             ` Yasuaki Kudo
2022-08-14  9:53             ` Phil
2022-08-14 22:03               ` Yasuaki Kudo
2022-08-15 20:50                 ` Phil
2022-08-25 18:37                   ` Olivier Dion via
2022-08-26  6:40                     ` Yasuaki Kudo
2022-10-12  9:55                     ` Ade Malsasa Akbar
2022-10-12 10:18                       ` Olivier Dion via
2022-08-26  7:24                 ` Ricardo Wurmus
2022-08-31  1:42                   ` Thompson, David
2022-08-31  6:33                     ` Ricardo Wurmus
2022-08-31 10:46                       ` [EXT] " Thompson, David
2022-08-31 11:42                         ` Olivier Dion via
2022-08-31 12:54                           ` Thompson, David
2022-09-05 19:38                         ` [EXT] " Ludovic Courtès
2023-01-23 15:34                           ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Giovanni Biscuolo
2023-01-23 16:48                             ` Przemysław Kamiński
2023-01-23 17:59                               ` Wojtek Kosior via
2022-09-05 19:42               ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03               ` zimoun
2022-10-08 16:23                 ` Phil
2022-10-10  7:58                   ` zimoun
2022-10-10 10:30                     ` (
2022-10-10 10:49                       ` zimoun
2022-10-10 19:35                     ` Phil

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=874jyy3bxh.fsf@laura \
    --to=help-guix@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=yasu@yasuaki.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.
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).