From mboxrd@z Thu Jan 1 00:00:00 1970 From: sirgazil Subject: Re: How to present Guix to a wider audience Date: Wed, 15 Jan 2020 12:44:29 -0500 Message-ID: <16faa4e8277.129e885d565438.6999666921160208292@zoho.com> References: <878smq41kg.fsf@ambrevar.xyz> <874kwyp9hi.fsf@ambrevar.xyz> <87blr5w0x7.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:47696) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irmif-0005wM-En for help-guix@gnu.org; Wed, 15 Jan 2020 12:44:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1irmie-0000oX-66 for help-guix@gnu.org; Wed, 15 Jan 2020 12:44:41 -0500 Received: from sender4-pp-o91.zoho.com ([136.143.188.91]:25199) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1irmid-0000mH-Tb for help-guix@gnu.org; Wed, 15 Jan 2020 12:44:40 -0500 In-Reply-To: <87blr5w0x7.fsf@ambrevar.xyz> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: Pierre Neidhardt Cc: help-guix Hi, Pierre ---- On Wed, 15 Jan 2020 03:59:00 -0500 Pierre Neidhardt wrote ---- > Thank you all for the reviews and the kind feedback! >=20 > It seems that the draft was met with success for now. > So what about including it on Guix' website, maybe with a big link to it > on the front page? =20 I think the problem of "What is Guix?" should be solved before doing that (= see https://lists.gnu.org/archive/html/help-guix/2020-01/msg00002.html). Personally, I think GNU Guix and its related operating system should be pre= sented separately. I think that GNU Guix is not a software that needs to be explained to the a= verage computer user. GNU Guix, in my opinion, is a software for system adm= inistrators and developers in any field, and it would be good to present it= clearly to them in general and provide explanations for particular fields = whenever necessary (that's what the section "GNU Guix in your field" in the= home page was designed for). Even though one of GNU Guix goals is to empower users, average users are mo= re into installing and removing application, and that's about it. Ideally, = not using a command-line interface directly but a graphical user interface = (e.g. an app store). The operating system, on the other hand, should be presented to average use= rs, and it should be called simply GNU. With this I mean that the GNU proje= ct should use GNU Guix to generate downloadable installers of what they cal= l the GNU Operating System in their home page and distribute these installe= rs through the GNU.org website. The pages of GNU.org should be updated acco= rdingly and focus on presenting the GNU operating system to the general pub= lic. This would include adding high-level information of the features GNU G= uix brings with it (reproducibility, bootstrappability, etc.) which would d= ifferentiate GNU from other systems. For advanced uses of the system that r= equire deeper understanding of GNU Guix, advanced users should be directed = to the GNU Guix subdomain. The rest of the current Free Software Distributi= ons (Trisquel, PureOS, Parabola, etc.) would still be listed in GNU.org as = alternative distributions of the GNU Operating System. I know that RMS oppo= sed to this idea a couple of years ago (https://lists.gnu.org/archive/html/= gnu-system-discuss/2014-11/msg00002.html), but I think this should be done. I think this separation could make it easier to outreach to potential users= of both artifacts, the OS and the "software environment manager". Calling = the OS just GNU would also help differentiate this system from what the gen= eral public call "linux".=20 --- https://sirgazil.bitbucket.io/