unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
	guix-devel@gnu.org
Subject: Re: GNU Guix 1.4.0 released
Date: Tue, 03 Jan 2023 13:42:39 -0500	[thread overview]
Message-ID: <87sfgrmpcw.fsf@dismail.de> (raw)
In-Reply-To: <83cc454a4b45e59cda4606cb4f313282@libre.brussels> (indieterminacy@libre.brussels's message of "Tue, 03 Jan 2023 17:09:26 +0100")

indieterminacy <indieterminacy@libre.brussels> writes:

> On 03-01-2023 10:08, Ludovic Courtès wrote:
>> Hi!
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>> 
>>> Congrats, and yay!  It's a hell of a release! :-) Let's try to make more
>>> punctual ones from now on, and also try to lower the amount of manual
>>> labor producing one incurs (by streamlining the process), as speaking
>>> for me, this was one of the reasons I kept putting it back.
>> Definitely, let’s see how we can make the process smoother.
>> In my experience though, a lot of the work is coordination: keeping
>> track of what needs to be done, open bugs, calling for testing, etc.
>> I think we should start thinking about the next release, forming a
>> small release team, and I’ll be happy to mentor!
>> Thanks,
>> Ludo’.
>
> Out of curiosity, have you ever approached developing a release from the
> perspective of doing documentation first?
>
> For example, test driven approaches like BDD or TDD have allowed the
> expectations and examples to be worked out first and the the implementation
> built to form it.
>
> More practically, theres a recent thread concerning different approaches and
> priorities concerning syntaxes. Also, if during 1.5 there were articulations
> regarding how existing behaviour does not conform with desired behaviour then it
> may become easier to divide up tasks into chunks for teams or individuals to
> work on.
>
> With idealised documentation in place this could provide a point of motivation
> for developers and avoid any fatigue once the solution is in place as the
> /drudgery/ of explaining how things work and how they can be used had been
> worked out in advance.

What areas does guix need more documentation?  To answer that question
for myself, I might say more gexp examples.  Though unmatched-paren is
working on a series of blog posts to dive really deep into that topic.

> In any case, while I cannot comment on the tactics within the OpenBSD community
> I always considered it a noble thing that no improvements we put into their OS
> until the features were correctly documented.
>

While OpenBSD does a pretty good job of documenting everything, I would
also chime in and say that Guix does a fantastic job of translating the
existing documentation into other languages. What do we have
documentation in English, German, French, and significant parts in
Russian and some asian languages. That's pretty stellar!

>
> Thanks everybody with your work on 1.4.0 !


  reply	other threads:[~2023-01-03 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:25 GNU Guix 1.4.0 released Ludovic Courtès
2022-12-27  3:37 ` Maxim Cournoyer
2023-01-03  9:08   ` Ludovic Courtès
2023-01-03 15:08     ` Maxim Cournoyer
2023-01-03 16:09     ` indieterminacy
2023-01-03 18:42       ` Joshua Branson [this message]
2023-01-03 20:35         ` indieterminacy
2023-01-03 23:16         ` indieterminacy
2023-01-05  9:57     ` Simon Tournier
2023-01-09 17:19       ` Setting up the release team Ludovic Courtès
2023-01-14 12:04       ` GNU Guix 1.4.0 released Tobias Platen

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=87sfgrmpcw.fsf@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=indieterminacy@libre.brussels \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.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.
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).