From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Re: Outreachy project infrastructure Date: Wed, 21 Nov 2018 16:34:16 +0100 Message-ID: <0aafd98124b2ac6f3236fc070166e371@lepiller.eu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54165) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPUWG-00069H-6X for guix-devel@gnu.org; Wed, 21 Nov 2018 10:34:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPUWC-0003b2-Ui for guix-devel@gnu.org; Wed, 21 Nov 2018 10:34:24 -0500 Received: from lepiller.eu ([2a00:5884:8208::1]:36798) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gPUWC-0003ZD-Kq for guix-devel@gnu.org; Wed, 21 Nov 2018 10:34:20 -0500 Received: from webmail.lepiller.eu (static-176-182-42-79.ncc.abo.bbox.fr [176.182.42.79]) by lepiller.eu (OpenSMTPD) with ESMTPSA id cf36bc09 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Wed, 21 Nov 2018 15:31:59 +0000 (UTC) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org 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