From: Phil <phil@beadling.co.uk>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Benjamin Slade" <beoram@gmail.com>,
"Olivier Dion" <olivier.dion@polymtl.ca>,
help-guix@gnu.org
Subject: Re: Enterprise Guix Hosting?
Date: Mon, 15 Aug 2022 21:50:00 +0100 [thread overview]
Message-ID: <87zgg5p6yv.fsf@beadling.co.uk> (raw)
In-Reply-To: <47774701-8E8E-4185-9DB9-7E5D7F91ACD2@yasuaki.com>
Yasuaki Kudo writes:
> What you wrote makes so much sense and sounds very familiar because I had similar discussions with my partners at our worker coop!
>
> Sometime soon perhaps we can discuss in a video chat or something?
Sure - keep us in the loop.
> We would like to do this alongside our regular paid software development for existing clients. Once we have acquired enough scripts, knowhow and the enthusiasts among our colleagues, we can spin it off and sell it as a service/consultation! (software will stay as Libre and Free - enterprise users would not be interested otherwise )
Where I work Guix is a tool we use in IT, rather than part of the
product we package/sell. This means I hope much of what we have learned
in terms of extending and using Guix will end-up open and freely
available over time - some in Guix itself. I don't see us offering
services or consultation in Guix as we're not a pure IT company.
However, I am interested in seeing Guix and Guix services gaining a
foothold in the commercial space, and exchanging ideas around this - as
well as growing it in academia too.
next prev parent reply other threads:[~2022-08-15 20:50 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
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 [this message]
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=87zgg5p6yv.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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).