all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: GNU Guix Video Documentation
Date: Thu, 25 Oct 2018 23:53:34 +0200	[thread overview]
Message-ID: <20181025235334.7ebf5970@alma-ubu> (raw)
In-Reply-To: <CAE4v=piWFt=i1hwPZ=xBStaUvn+a9-_JbZWieBqp9B0TpTNU7Q@mail.gmail.com>

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

On Thu, 25 Oct 2018 14:39:40 +0200
Gábor Boskovits <boskovits@gmail.com> wrote:

> Hello Guix,
> 
> I've prepared a preliminary version of the graph of minimal
> requirements of this project,
> it is mostly abstract for now, but I would like to hear the opinions,
> or possible additions to this.
> So here it is. WDYT?

Hi Gábor,

since I first heard from the realization of the Video/Outreachy
project, I found this procedure a bit abstract and I fear that the
outcome would be a bit boring when done like that. Especially the part
"images" is what I find suspicious, maybe I understand it wrong and I
have to convinced into some direction: Do you mean by that still
images/screenshots that will then be shown some duration (in the range
of seconds), like slideshows with text-slides and screenshots
intermixed? That is then mixed with subtitles and/or audio recordings.

I expected more like a screen cast: A life hacking session with
comments on what's going on, why doing a step, opening a brower and
show where to find docs. Of cause this has to be well prepared and some
parts have to be cut out in order to be not too tedious (half an hour
gcc log output during compilation is not so interesting for some
people).

[I thought of maybe combining it with someone moderating, i.e. a person
filmed who is explaining what they are doing. Though we need to be
careful to not push anyone into that direction who doesn't want. Maybe
it's better to drop that idea.]

What I'm next missing is a set of tasks that we want to be
video-documented. Or should that be part of the internship? I think it
is more on our side to define the requirements.

How and on which platform should the final result be presented?
This includes freedom, privacy and technical aspects and is a
question of acceptence/broadness of people watching it. Depending on the
choice, could that affect the preparation process (for example,
subtitle format, video-container format, audio-channels/translations,
automatic text2subtitle conversation)?

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-10-25 21:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 12:39 GNU Guix Video Documentation Gábor Boskovits
2018-10-25 21:53 ` Björn Höfling [this message]
2018-10-26  4:13   ` Ricardo Wurmus
2018-10-26  6:22     ` Gábor Boskovits
2018-10-26  9:59     ` Giovanni Biscuolo
2018-10-26 10:00     ` Björn Höfling
2018-10-26 11:09       ` Gábor Boskovits
2018-10-28  0:32       ` Laura Lazzati
2018-10-28  9:13         ` Gábor Boskovits
2018-10-28 19:14           ` Laura Lazzati
2018-10-28 20:19             ` Gábor Boskovits
2018-10-28 23:26               ` Laura Lazzati
2018-10-29  8:17                 ` Gábor Boskovits
2018-10-29 12:47                   ` Laura Lazzati
2018-10-29  9:10                 ` Björn Höfling
2018-10-29 12:49                   ` Laura Lazzati
     [not found] <CAG=FMuXO7X0j-D_SMWNgxO0p_0xsyJ_eahDGDjtuv465Y3Xk0A@mail.gmail.com>
2018-10-25  6:17 ` Björn Höfling
2018-10-25  9:18   ` Gábor Boskovits
2018-10-25 16:25     ` Larissa Leite
2018-10-25 16:52       ` Gábor Boskovits
2018-10-29  9:31         ` Gábor Boskovits

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=20181025235334.7ebf5970@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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.