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: Sun, 3 Jan 2016 13:49:43 -0500 [thread overview]
Message-ID: <20160103184943.GC29254@jasmine> (raw)
In-Reply-To: <87bn92vjc2.fsf@gnu.org>
On Sun, Jan 03, 2016 at 03:17:01PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > 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.
>
> I agree. If someone volunteers to write transcripts of the available
> videos, we could put them online (but obviously that’s quite a bit of
> work!).
>
> > 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".
>
> The liberating, dependable, and hackable items on the front page link to
> overviews in the manual, notably the “Features” node. Maybe a good
> start would be to improve them?
>
> > I also liked some blog posts by Andy Wingo and Christopher Allan Webber,
> > although those posts don't explain "the whole picture".
>
> Agreed, blog posts like these and those of David and Ricardo are very
> nice, because they show concrete use cases.
>
> They’re also useful for someone knowledgeable about the project because
> they clearly show parts that are confused, badly documented, or that
> somehow fail to address the problems people are having.
>
> I would invite the bloggers among us to do more of these. :-)
How about linking these blog posts from the site? That could be a good
way to catch the attention of new visitors.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2016-01-03 18:49 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
2016-01-03 14:17 ` Ludovic Courtès
2016-01-03 18:49 ` Leo Famulari [this message]
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
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=20160103184943.GC29254@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 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).