all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Guix website
Date: Fri, 1 Jan 2016 16:23:30 -0500	[thread overview]
Message-ID: <20160101212330.GB11284@jasmine> (raw)
In-Reply-To: <87d1tll4aj.fsf@gnu.org>

On Fri, Jan 01, 2016 at 04:15:16PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > Some of the video-recorded presentations have been a very nice
> > introduction. Perhaps we could embed one on the home-page. If we do
> > that, I could help transcribe it, with the slides embedded, to increase
> > accessibility.
> 
> There’s already a video on the home page.  :-)  I wonder if we should
> switch to a newer talk, such as <https://gnunet.org/guix2015video>.

Haha, I guess I never scroll down. Everything I need is "above the
fold".

> 
> That said, probably few people bother watching a 45mn video “just to get
> a feel.”  So it may be that we still need to improve the web site’s
> message.

Yes, I personally hate watching videos and listening to podcasts. I only
do it when there is no transcript and I am on a long bus or train ride
and can't concentrate on working. I personally found that video to be a
very good explanation of the problems addressed by Guix and the
solutions offered. As well as the newer video you mentioned.

A transcript next to slides [0] can be read in less time than 45
minutes. It can also be skimmed, searched, and anchor-linked.

That wouldn't be a perfect solution but it could be done "almost now".

A number of the ...unusual questions people have asked about Guix
demonstrate a near total lack of knowledge about the project's goals and
design. We need an overview like that provided by the videos. The manual
is more of a "how-to".

I also liked some blog posts by Andy Wingo and Christopher Allan Webber,
although those posts don't explain "the whole picture".

[0] I like this format, with bigger pictures:
http://idlewords.com/talks/website_obesity.htm

> 
> Ludo’.

  reply	other threads:[~2016-01-01 21:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 11:18 Guix website Pjotr Prins
2015-12-30 14:32 ` Ni*
2015-12-31 17:42 ` Leo Famulari
2016-01-01  6:49   ` Pjotr Prins
2016-01-01 15:17     ` Ludovic Courtès
2016-01-03 16:35       ` Luis Felipe López Acevedo
2016-01-03 18:48         ` Leo Famulari
2016-01-01 15:56     ` Christopher Allan Webber
2016-01-01 15:15   ` Ludovic Courtès
2016-01-01 21:23     ` Leo Famulari [this message]
2016-01-03 14:17       ` Ludovic Courtès
2016-01-03 18:49         ` Leo Famulari
2016-01-03 22:32           ` Ludovic Courtès
2016-01-04  4:48           ` Pjotr Prins
2016-01-04 15:15             ` Ludovic Courtès
2016-01-03 18:55     ` Christopher Allan Webber
2016-01-04 15:16       ` Ludovic Courtès
2016-01-04 16:46         ` Pjotr Prins
2016-01-07 18:06           ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2016-10-25 19:41 rennes
2016-10-26  8:21 ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160101212330.GB11284@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.