unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org, Laura Lazzati <laura.lazzati.15@gmail.com>
Subject: Re: We need your feedback of the documentation videos!
Date: Tue, 30 Jul 2019 19:12:50 +0200	[thread overview]
Message-ID: <878ssffnu5.fsf@nckx> (raw)
In-Reply-To: <87blxbftty.fsf@nckx>

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

Laura, everyone,

More badly-written notes from watching the other half of these 
fine video shows.  I'll try to submit some patches myself, if I 
manage.  Many are just me thinking aloud, not worth delaying a 
release.

03-help:
- 00:40 It's a shame that Paul made such a good job of reading our 
  old URL :-(  All URLs in this video (and the others; fun!) 
  should be tested for 404s & 308s before releasing the videos, 
  although that's eminently scriptable.

- 01:10 http://guix.gnu.org/help/ has changed. 
  http://guix.gnu.org/contact/ would now make a better screenshot 
  to match the audio at this timestamp.

- 02:15 Was the title ‘subscribing to a mailman’ intentional? 
  The conventional and boring choice would be ‘mailing list’ or 
  just ‘list’.

- 03:44 We can now add a ‘link’ to logs.guix.gnu.org, to give 
  new users a sense of the place before they jump in, which can be 
  intimidating.
Since this logging is not done by Freenode, I'd move it to the 
bottom of the slide as its own top-level item.

04-packaging-part-one:
- 00:13 This slide would be much easier to scan if both the arrows 
  and the commands were vertically aligned.  ‘get’ should be 
  capitalised.  ‘bootstrap’ is only ever run as ‘./bootstrap’. 
  Let's write ‘./pre-inst-env’ as well since it's not in $PATH.

<nckx cares too much about fonts>
In 02-everyday-use-part-two, commands like ‘guix install’ were 
set in the highly condensed sans-serif.  The serif font used here 
is a much better choice for commands (and more efficient than 
monospace).  Whatever the choice, I think it should be 100% 
consistent across videos.
</nckx cares too much about fonts>

04-packaging-part-two:
The file names should sort spontaneously, for examply by using 
digits: 04-packaging-part-2.  Even if this weren't an issue on 
A/V.gnu.org, people may upload them elsewhere if we're lucky, and 
04-packaging-part-three currently plays before this one.

00:30 ‘Using’ → ‘Use’ to match the rest.
‘i.e.’ should be ‘e.g.’, or drop it entirely because:
‘R’ → ‘R packages’.  If that really can't be made to fit 
we'll have to rewrite that; ‘R are’ doesn't work *and* sounds 
silly.

- 01:15 I'm afraid this could be taken as a joke.  Maybe expand 
  the RHS of the ‘algorithm’ to include the steps later covered 
  in part 3?  They could be greyed out to show that we'll focus on 
  ‘guix import’ in this video.
More ‘backwards’ font usage: serif text, sans-serif command.

- 02:25 ‘open with a text editor <> file’ → ‘open the <> file 
  with a text editor’.
Personally, I'd like to see ‘append alphabetically’ (or ‘add 
alphabetically’, since ‘append’ can be mistaken to mean ‘at 
the end’).  The audio will still say ‘append’ but that's all 
right.

04-packaging-part-three:
- 00:20 The difference between ‘2) Check’ and ‘3) Test’ is not 
  clear to me.  The audio doesn't explicitly mention these 4 
  steps.  Using lone imperatives can be powerful, but these just 
  confuse me.
*Maybe*: if we chose expand the ‘packaging algorithm’ in part 2, 
 we could re-use that here, with the other half greyed-out.
There also appears to be an extra space before Test, but this 
might not be there in the code.

- 00:55 Apparent extra space before Check (which should be ‘Check 
  for’), same for Gender in the next slide.  This always seems to 
  happen on the 3rd item.  Coincidence?
The font rendering in general is just… off, but that's obviously 
not your fault.
Typo: ‘Gender-neutral’.
Here, too, I find the ‘random’ arrow positioning and 
inconsistent spacing (like ‘    etc/’ at 01:50) a bit 
distracting.

Lists like these always sound so negative.  I love the videos.

T G-R

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

  reply	other threads:[~2019-07-30 17:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 15:11 We need your feedback of the documentation videos! Laura Lazzati
2019-07-16 17:40 ` pelzflorian (Florian Pelz)
2019-07-17  6:31 ` Dimakakos Dimos
2019-07-17  7:55   ` pelzflorian (Florian Pelz)
2019-07-30 14:37     ` pelzflorian (Florian Pelz)
2019-07-17  7:11 ` Tanguy Le Carrour
2019-07-17  9:44 ` Ricardo Wurmus
2019-07-30 13:26   ` Laura Lazzati
2019-07-30 15:03     ` Tobias Geerinckx-Rice
2019-07-30 17:12       ` Tobias Geerinckx-Rice [this message]
2019-07-30 14:06   ` pelzflorian (Florian Pelz)
2019-08-08 15:04   ` Laura Lazzati
2019-08-08 15:48     ` Ricardo Wurmus
2019-08-13 18:03       ` Laura Lazzati
2019-08-25 18:55         ` Laura Lazzati
2019-10-17  4:34           ` pelzflorian (Florian Pelz)
2019-10-19 20:13             ` Ludovic Courtès
2019-10-19 21:00               ` pelzflorian (Florian Pelz)
2019-10-22 12:05                 ` pelzflorian (Florian Pelz)
2019-10-22 16:25                   ` sirgazil
2019-10-22 18:59                     ` pelzflorian (Florian Pelz)
2019-10-23 11:49                       ` pelzflorian (Florian Pelz)
2019-10-23 14:33                         ` sirgazil
2019-10-25  6:35                       ` pelzflorian (Florian Pelz)
2019-10-25  8:12                         ` pelzflorian (Florian Pelz)
2019-10-25 14:25                           ` sirgazil
2019-10-25 20:32                         ` Ludovic Courtès
2019-10-25 21:58                           ` pelzflorian (Florian Pelz)
2019-10-26 14:29                             ` pelzflorian (Florian Pelz)
2019-10-27 19:47                               ` sirgazil
2019-10-28  7:41                                 ` pelzflorian (Florian Pelz)

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=878ssffnu5.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=laura.lazzati.15@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).