From: Leo Famulari <leo@famulari.name>
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix website
Date: Sun, 3 Jan 2016 13:48:52 -0500 [thread overview]
Message-ID: <20160103184852.GB29254@jasmine> (raw)
In-Reply-To: <1574698c9c2377a12606e2a196ded416@openmailbox.org>
On Sun, Jan 03, 2016 at 11:35:19AM -0500, Luis Felipe López Acevedo wrote:
> On 2016-01-01 10:17, ludo@gnu.org wrote:
> >Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> >
> >>On Thu, Dec 31, 2015 at 12:42:44PM -0500, Leo Famulari wrote:
> >>>After the last exchange on help-guix, I think you are right. We really
> >>>need to do more to explain what Guix can do.
> >>>
> >>>Hackability and dependability only go together because of the
> >>>architecture of the system. As for liberating, I think of the ideas of
> >>>negative and positive liberty. Positive liberty in this case ==
> >>>hackability.
> >>>
> >>>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.
>
>
> I thought about this too. I wanted something like:
>
> - /guix/media/: list video and audio recordings from presentations.
> - /guix/media/ITEM/: show the ITEM with transcription.
>
> Transcriptions are a huge job though. But I'm sure Guix will gain
> contributors that will help with things like these in the future.
Transcriptions ARE a huge job but I would be willing to do one if it was
decided that it would be useful. I'm just putting it out there. Of
course, there may be better ways to spend the time.
>
>
> >>How about creating two websites. One for hackers, one for users?
> >
> >I don’t think this is a good idea. But maybe we could list use cases on
> >the front page, with links to tutorial-style info?
> >
> >For instance, “set up a development environment” would link to something
> >that explains how to use ‘guix environment’ in a development context;
> >“deploy an OS” would link to ‘guix system’, etc.
>
>
> I like that idea.
>
>
> >Then we’d need input from Felipe or some other web design expert as to
> >how to integrate it.
>
>
> I wish I could help, but I can't right now. All I can do is take note of
> this and hopefully come back later with some design proposals :)
>
>
> --
> Luis Felipe López Acevedo
> http://sirgazil.bitbucket.org/
>
next prev parent reply other threads:[~2016-01-03 18:48 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 [this message]
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
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=20160103184852.GB29254@jasmine \
--to=leo@famulari.name \
--cc=felipe.lopez@openmailbox.org \
--cc=guix-devel@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.