unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Csepp <raingloom@riseup.net>
To: Daniel Riesner <danielriesner@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: Question about the use of GNU Guix in production
Date: Wed, 07 Sep 2022 18:04:04 +0200	[thread overview]
Message-ID: <87sfl341bf.fsf@riseup.net> (raw)
In-Reply-To: <846cf1d5-1239-814e-2b2a-eb07536bd72e@posteo.net>


Daniel Riesner <danielriesner@posteo.net> writes:

> Hello,
>
> although for now I only quickly tried GNU Guix in a vm, but more in
> depth have read the well written GNU Guix manual, I'm quite fascinated
> by it. Having a bit of a background in DevOps working among other
> things with infrastructure as code tool Terraform and the method of
> GitOps, I came to like declarative configuration. To me it seems for
> operating services, it brings e.g. greater transparency in
> collaboration and better ways to test and rollback changes in case of
> failure. Concerning the more political aspects, in many places I
> prefer free software and more decentralized services. Since I'm
> currently looking for a job, besides academic institutions, are there
> any companies known to use GNU Guix, which maybe even have open
> positions preferably in Germany or remote? Or do you maybe know of any
> places where such offers are shared as it is done e.g. for NixOS in
> their discourse forum?
>
> Best wishes
> Daniel Riesner

I've seen at least one job offer on one of the mailing lists (probably
the developer one), but it's not a common sight.


  reply	other threads:[~2022-09-07 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 14:04 Question about the use of GNU Guix in production Daniel Riesner
2022-09-07 16:04 ` Csepp [this message]
2022-09-07 17:09   ` Philip Beadling
2022-09-23 16:48     ` Daniel Riesner
2022-09-23 16:43   ` Daniel Riesner

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=87sfl341bf.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=danielriesner@posteo.net \
    --cc=help-guix@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.
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).