From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: Outreachy project infrastructure
Date: Wed, 21 Nov 2018 16:34:16 +0100 [thread overview]
Message-ID: <0aafd98124b2ac6f3236fc070166e371@lepiller.eu> (raw)
In-Reply-To: <CAPNLzUMOaarQ5V4QPMt+cTT5HDv2U=6Tb3udkB7qvAUn+tu-HQ@mail.gmail.com>
Le 2018-11-21 15:37, Laura Lazzati a écrit :
> Hi everyone! :)
>
> I'm going back to all the previous emails, and the graph, and write
> down a summary in this thread, so that it does not end up messy, and
> we can discuss it here. Probably, I will be asking questions also
> about the graph, and also writing what we were thinking about the
> tools that would be used. Also asking if someone could suggest a tool
> that they know. I will do my research, of course, but it is new to me.
For subtitles, I'd like to recommend using aegisub. We have a package
for
it in Guix, but I'm not entirely sure it is functional. I think we need
to
document the way to make translations for the video content, the audio
part
and add new subtitles. So I think we have to automate the process as
much
as possible so translators can work on producing the localised content
and get it automatically integrated into a localised version of the
video.
For translating audio, we will probably produce a translated script, so
I'd like to use one of the formats supported by po4a if possible. Since
the content of these files is not going to change often and they won't
have a lot of structure to preserve during translations, it's also
possible to not use a tool like gettext and simply translate files
directly. I don't know.
I think we should also create subtitles for English, so people can
enjoy the video even without audio.
Of course I volonteer for the French translation :)
>
>
> I don't like duplicating things, but Gabor's summary was - thank you
> for this, I am just quoting it so that we have it in this thread - :
>
> Now that we have our intern announced I would like to bring this
> thread back to life.
>
> So regarding the Outreachy Project for Creating Video Documentation
> for GNU Guix,
> we come to a point where we should set up the priorities:
> 1. What types of videos should be created first:
> a. introducing concepts,
> b. practical howtos.
> 2. What audience to target:
> a. people not yet interested in guix
> b. people new to guix
> c. users
> d. developers.
> 3. What topics to cover first.
>
> What we have so far:
>
> Based on Julien's suggestions:
> * Focus on more practical howtos aimed at people new to guix.
> ** installing guix on a foreign distro
> ** installing guixsd
> ** using guix: installing, upgrading and removing packages
> ** guix pull
> ** MAYBE guix gc
> * Developers (not guix, but general devs)
> ** environments vs profiles
> ** developing on guixsd
> ** "getting back to work" when something goes wrong
> ** roll-back profile, system-profile, guix
>
> Additional questions based on Laura's suggestions:
> * Should we aim some videos at contributors?
> * Should we create videos related to getting help or troubleshooting?
>
> Regards!
> Laura
next prev parent reply other threads:[~2018-11-21 15:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:51 Outreachy project infrastructure Gábor Boskovits
2018-11-21 14:37 ` Laura Lazzati
2018-11-21 15:34 ` Julien Lepiller [this message]
2018-11-21 15:19 ` Ricardo Wurmus
2018-11-21 20:18 ` Laura Lazzati
2018-11-21 22:28 ` Ricardo Wurmus
2018-11-22 1:13 ` Laura Lazzati
2018-11-22 12:32 ` Thorsten Wilms
2018-11-22 13:12 ` Ricardo Wurmus
2018-11-22 14:23 ` Thorsten Wilms
2018-11-22 20:11 ` Björn Höfling
2018-11-23 1:54 ` Laura Lazzati
2018-11-23 9:04 ` Ricardo Wurmus
2018-11-23 10:24 ` Gábor Boskovits
2018-11-23 11:01 ` Ricardo Wurmus
2018-11-23 11:38 ` Gábor Boskovits
2018-11-23 12:27 ` Ricardo Wurmus
2018-11-25 23:08 ` Björn Höfling
2018-11-26 0:30 ` Laura Lazzati
2018-11-26 14:07 ` Björn Höfling
2018-11-26 15:40 ` Laura Lazzati
2018-11-29 15:19 ` Laura Lazzati
2018-11-29 15:36 ` Ricardo Wurmus
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=0aafd98124b2ac6f3236fc070166e371@lepiller.eu \
--to=julien@lepiller.eu \
--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 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).