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

Hello!

Andrew Tropin <andrew@trop.in> skribis:

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

[...]

>> 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.

I think it’d be ideal to have the post before the release, so users know
what they’re getting.  :-)

It’s completely fine if there are still missing features, etc. IMO;
it’ll keep growing and there can be another post later.

> 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.

Oh I’m sorry to read that.  I certainly don’t want to add more on your
plate or to have you feel pressured to do more.

I think we can take our time on this; we can clarify in the manual and
announcement what it is that users are getting when the release is out.

(To be clear, the review process has been a burden on me too, and it’s a
strong commitment from the Guix maintainers going forward.)

[...]

> 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.

Yeah, there’s no style guide, but on the up side, there’s established
practice with system services that hopefully we can follow in most
cases.

Anyway, recovering from burnout and making sure it doesn’t happen again
should be the priority.

Thanks for your feedback,
Ludo’.


  reply	other threads:[~2021-12-20 22:20 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
2021-12-20 22:20   ` Ludovic Courtès [this message]
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=87pmpqdiln.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andrew@trop.in \
    --cc=guix-devel@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).