From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Wilms Subject: Re: Videos Date: Tue, 19 Jun 2018 11:32:01 +0200 Message-ID: <5f4ba527-acf0-b5c7-5450-329dbae50f70@freenet.de> References: <87in76qzzk.fsf@elephly.net> <87sh5jvn29.fsf@elephly.net> Reply-To: t_w_@freenet.de 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]:38652) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVD1i-0007Oj-U6 for guix-devel@gnu.org; Tue, 19 Jun 2018 05:34:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVD1e-0006mw-0N for guix-devel@gnu.org; Tue, 19 Jun 2018 05:34:14 -0400 Received: from mout3.freenet.de ([2001:748:100:40::2:5]:40870) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVD1d-0006m4-PL for guix-devel@gnu.org; Tue, 19 Jun 2018 05:34:09 -0400 Received: from [195.4.92.142] (helo=mjail2.freenet.de) by mout3.freenet.de with esmtpa (ID t_w_@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fVD1Z-0005sE-NU for guix-devel@gnu.org; Tue, 19 Jun 2018 11:34:05 +0200 Received: from [::1] (port=52644 helo=mjail2.freenet.de) by mjail2.freenet.de with esmtpa (ID t_w_@freenet.de) (Exim 4.90_1 #2) id 1fVD1Z-0007Ui-Jb for guix-devel@gnu.org; Tue, 19 Jun 2018 11:34:05 +0200 Received: from mx7.freenet.de ([195.4.92.17]:55392) by mjail2.freenet.de with esmtpa (ID t_w_@freenet.de) (Exim 4.90_1 #2) id 1fVCza-0005jS-1r for guix-devel@gnu.org; Tue, 19 Jun 2018 11:32:02 +0200 Received: from p200300e4f3d62b0002e029fffe32e625.dip0.t-ipconnect.de ([2003:e4:f3d6:2b00:2e0:29ff:fe32:e625]:52658) by mx7.freenet.de with esmtpsa (ID t_w_@freenet.de) (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256) (port 465) (Exim 4.90_1 #2) id 1fVCzZ-0006Dq-Rq for guix-devel@gnu.org; Tue, 19 Jun 2018 11:32:02 +0200 In-Reply-To: <87sh5jvn29.fsf@elephly.net> Content-Language: en-GB 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 On 18.06.2018 22:47, Ricardo Wurmus wrote: > What are good first topics that we could introduced in self-contained > videos? The goal is to show a useful feature (one or two closely > related features per video) without making things confusing. > We don’t need to start with this abstract topic. Maybe > it’s better to show features first. If the videos are supposed to not only be of help to those who already decided to give Guix a spin, but also to encourage others to do so, they should perhaps be scenario [/ use case / problem / story] based. With a flow like this: Scenario -> the What of a set of helpful features -> the How As starting point, we may assume the viewer isn't even aware of issues with package management ala .deb. Even worse, if they are more accustomed to Windows, OSX, IOS, Android, they might not even see the advantages of typical Linux package management. However, the comparison to other systems comes with the risks of becoming long-winded and to appear to disparage the efforts of others. Topics should likely start on a per-package level, then move to the system level. Likewise from user to developer. If a user doesn't already know which piece of software they are interested in, there's a step even before installation ... let's call it discovery. Seems all that could be mentioned here is `guix package -s term`. I just tried to come up with a nice example, but even knowingly aiming at Inkscape, `guix package -s svg` or `... "vector graphics"` speaks more of a problem than a solution. If only one could filter for library / cli tool / graphical application. With protagonist P and software S: Package Discovery P wants to accomplish Thing and looks for matching Free Software. Installation P wants to use S and thus installs it, without worrying about any dependencies. P may lack root privileges. Not even a power outage can faze P. Updates and rollbacks P updates S, then finds out something about S doesn't work as desired anymore. P rolls S back to the previous version without skipping a beat Removal P doesn't use S anymore. P removes S and it is as if it was never installed. System Global updates and rollback P likes to keep all the software up-to-date and secure. P doesn't have to do much to accomplish this. If P tinkers with system configuration and ends up with its currents state broken, a rollback is not far. Garbage collection Rollback are nice, a full HD isn't ... Multiple versions side by side S1 needs library L version 1.2, S2 needs L at 2.1. No sweat! Duplication/Migration (system configuration and manifest) P bought a new computer. Getting it ready won't take long ... Development Watertight handling of dependencies Inheriting and modifying packages Environments ... -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/