unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>, Xinglu Chen <public@yoctocell.xyz>
Subject: Re: SSH service for Guix Home
Date: Thu, 16 Dec 2021 18:43:05 +0300	[thread overview]
Message-ID: <87r1acwo6u.fsf@trop.in> (raw)
In-Reply-To: <878rwlu4uz.fsf@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 3716 bytes --]

On 2021-12-15 18:59, Ludovic Courtès wrote:

> Hi Andrew,
>

Hi Ludovic!

> One service I miss for Guix Home is ‘home-ssh-service-type’, which is
> in the “original” Guix Home.
>
> Could you contribute a patch adding it?  (I could do it on your behalf,
> but it sounds more logical to let you handle it.)

Yep, I'll try to do it soon.

>
> Also, could you (or Xinglu, or Oleg) write a blog post for guix.gnu.org,
> targeting an audience who’s not familiar with this kind of tool, making
> it clear what the rationale is and what it can bring to “normal users”?
> It would be really helpful to have that published within a couple of
> weeks or so, before the next release.

I have a blog post task in my backlog, I want to upstream more home
services before publishing the post.  It's not a blocker, but a nice
thing to have.  There is another ongoing work, which I would like to
finish before making a post.

Another option is to publish this post some time after 1.4.0 release, so
everything I want will be finished to that moment.  I don't see reasons
to hurry, so it's a viable alternative too.

>
> Last, it’d be great to see the three of you (and more people!) back in
> action regarding Guix Home.  I understand that life sometimes gets in
> the way, but it seems that there’s been some confusion as to how to go
> forward—e.g., <https://issues.guix.gnu.org/51359#2>—which may partly
> explain why things stalled.  If there are patches waiting for review,
> also don’t hesitate to ping!

I burnt out a little during upstreaming process, it was quite slow and
painful at the beginning and increased maintanance burden of rde for me.
A little too early merge + uncoordinated changes of basic primitives and
service configurations also hit me quite hard and forced to spend some
time bringing rde back to working state without going a step further.

I took a break and after that started to cleanup small Guix Home issues,
develop/improve home services in rde repo and finally started to work on
new rde features.  Still feel a little burnt out and I try not to do
worse.


Now to more technical details:

When I started to work on Guix Home I explored different system services
configurations and tried to extract some common patterns, it was
relatively hard, cause of implementation inconsistencies.  I wrote
notes, extracted most common patterns and come with some approach for
writing service configurations.  During development of Guix Home it was
slightly changed, but most of the home service implementations are
consistent.

gexp -> file-like change done in Guix repo for shell service
configurations and text-config type partially breaks the ideas I have
about how services should be implemented.

To continue upstreaming home services from rde to Guix I would like and
actually need to have an established style guide on how to write service
configurations to make sure service implementations are consistent.  I
started to write a manual section, which we can collectively review,
discuss and adjust it to get such a style guide.  Cause of burn out and
a lot of unrewarding monkey work I've done recently it's a little hard
to focus on this task, but I'll try to send first drafts to mailing list
soon.

So there is some work happening, but maybe not so visible.


Sorry for being not very active on ML recently, hope after core-updates
merged now you have a little more free time, so we can faster reach the
agreement on service implementation style guide and more people will be
able to contribute high quality services for both Guix System and Guix
Home.

-- 
Best regards,
Andrew Tropin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  reply	other threads:[~2021-12-16 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 17:59 SSH service for Guix Home Ludovic Courtès
2021-12-16 15:43 ` Andrew Tropin [this message]
2021-12-20 22:20   ` Ludovic Courtès
2021-12-17 14:21 ` Xinglu Chen
2021-12-20 10:40   ` Andrew Tropin
2021-12-22  7:42     ` Xinglu Chen
2021-12-20 22:31   ` Ludovic Courtès
2021-12-22  7:43     ` Xinglu Chen

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=87r1acwo6u.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=public@yoctocell.xyz \
    /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).