all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: wisdomlight@protonmail.com
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: "help-guix\\\\@gnu.org" <help-guix@gnu.org>,
	"sirgazil@zoho.com" <sirgazil@zoho.com>
Subject: Re: How to present Guix to a wider audience
Date: Sun, 19 Jan 2020 15:57:07 +0000	[thread overview]
Message-ID: <VbzMbbhqcRrfKtznAV9v-Oy7Mmc60rDiy-tHrhwaVTN_s60FFpjxZTunzZCGLWzVglV8bt_lSDUTv_hKkagi5qIFNQDxW6XIh61HInrrP2k=@protonmail.com> (raw)
In-Reply-To: <XgHqrlPUwld-StdbW5SYgqN9kx64_4Q81xhDsbAn9igquzRBp0LwrkhCA5RIMk-MgmgNGMn8ylSlL92-aOw2wJEVBg5x1ZDyWr_4FmzPBiU=@protonmail.com>

Having worked with Guix for number of days with some issues - some of my own makings....
I cannot see how i can say to my grandmother install guix.
for the simplest reason that i found it very hard to find the software that i needed plus the software i needed if it was not on the guix store/farm was very difficult to understand how to install with chnnels etc.
So I am not sure about recommending Guix to beginners.


Sherab

Just like an experience in a dream
Everything I now enjoy
Will become a mere recollection
For what has past will not be seen again

Sent from ProtonMail, encrypted email based in Switzerland.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 19 January 2020 11:03, Todor Kondić <tk.code@protonmail.com> wrote:

> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, 15 January 2020 18:44, sirgazil sirgazil@zoho.com wrote:
>
> > Hi, Pierre
> > ---- On Wed, 15 Jan 2020 03:59:00 -0500 Pierre Neidhardt mail@ambrevar.xyz wrote ----
> >
> > > Thank you all for the reviews and the kind feedback!
> >
> > >
> >
> > > 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?
> >
> > I think the problem of "What is Guix?" should be solved before doing that (seehttps://lists.gnu.org/archive/html/help-guix/2020-01/msg00002.html).
> > Personally, I think GNU Guix and its related operating system should be presented separately.
> > I think that GNU Guix is not a software that needs to be explained to the average computer user. GNU Guix, in my opinion, is a software for system administrators 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 more 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 users, and it should be called simply GNU. With this I mean that the GNU project should use GNU Guix to generate downloadable installers of what they call the GNU Operating System in their home page and distribute these installers through the GNU.org website. The pages of GNU.org should be updated accordingly and focus on presenting the GNU operating system to the general public. This would include adding high-level information of the features GNU Guix brings with it (reproducibility, bootstrappability, etc.) which would differentiate GNU from other systems. For advanced uses of the system that require deeper understanding of GNU Guix, advanced users should be directed to the GNU Guix subdomain. The rest of the current Free Software Distributions (Trisquel, PureOS, Parabola, etc.) would still be listed in GNU.org as alternative distributions of the GNU Operating System. I know that RMS opposed 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 general public call "linux".
>
> I am sorry, but Guix should most definitively be presented to averagenix based users (the admins of their own/family workstations). It's like: "Look, now your grandmother, her cat and your dog can all install packages without knowing your sudo password!". This feature alone is highly appealing to some circles ;) .
> As for more "advanced" users, from the experience I had when talking about Guix to the unconverted hackers, they struggle to accept why is it so much better than the already hyped technologies that Just Work, such as Chef/Puppet and other CI/CD for automating installations (), Docker/Singularity on their own for building containers etc, especially because it is based on an 'exotic' language as Scheme (exotic was the exact word that has been used in a certain conversation with an experienced professional developer). Disclaimer: I started using Guix because it was based on Guile.
>
> Of course, different target groups should be, well, targeted with different aspects of Guix -- those that may appeal to them. And, there is more to Guix than just the pkg manager and the OS.
>
> Also, to be fair, Guix is the first complex program of the GNU system I am aware of that started making waves in modern times, so on the presentation front some things have already been done well.
>
> -   I am not an expert on this, so I am not sure whether Guix can fit in the same workflow with the mentioned tools, or is in a parallel, or an orthogonal universe.

  reply	other threads:[~2020-01-19 15:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 10:03 How to present Guix to a wider audience Pierre Neidhardt
2020-01-02 18:18 ` zimoun
2020-01-08 15:33   ` Pierre Neidhardt
2020-01-08 16:32     ` Ricardo Wurmus
2020-01-08 20:18     ` zimoun
     [not found]       ` <24DdUL_0dCHlf-Jsotb_z0Mxz7kuUpI_FeBoRrbgJUypYRxvic9u3GhPfBwAiz5ZGjRxITivscu59w_-BPA2cIY_wSbypis89M7Jb8AglBM=@protonmail.com>
     [not found]         ` <CAJ3okZ1CQ1zvbHnFT6EmB+yYFwcAszZ0baroyj03LzTK7AhBXw@mail.gmail.com>
2020-01-10  9:52           ` wisdomlight--- via
2020-01-10 12:19             ` Pierre Neidhardt
2020-01-02 19:20 ` Ricardo Wurmus
2020-01-08 15:26   ` Pierre Neidhardt
2020-01-14 11:23 ` Pierre Neidhardt
2020-01-14 15:58   ` Jack Hill
2020-01-14 17:00     ` Pierre Neidhardt
2020-01-14 21:01       ` Jack Hill
2020-01-14 23:44   ` Dimakakos Dimos
2020-01-15  0:07   ` Vagrant Cascadian
2020-01-15  8:52     ` Pierre Neidhardt
2020-01-15  0:20   ` Josh
2020-01-15  8:57     ` Pierre Neidhardt
2020-01-15  5:59   ` Arun Isaac
2020-01-15  8:53     ` Pierre Neidhardt
2020-01-15  8:59   ` Pierre Neidhardt
2020-01-15 17:44     ` sirgazil
2020-01-19 11:03       ` Todor Kondić
2020-01-19 15:57         ` wisdomlight [this message]
2020-01-21 21:49   ` ndre
2020-01-22 11:00     ` Pierre Neidhardt
2020-01-22 17:35       ` Pierre Neidhardt
2020-01-23 14:44         ` Kelsang Sherab
2020-01-23 21:25           ` Pierre Neidhardt
2020-02-11  7:45   ` Pierre Neidhardt
2020-02-11 17:38     ` Josh Marshall

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='VbzMbbhqcRrfKtznAV9v-Oy7Mmc60rDiy-tHrhwaVTN_s60FFpjxZTunzZCGLWzVglV8bt_lSDUTv_hKkagi5qIFNQDxW6XIh61HInrrP2k=@protonmail.com' \
    --to=wisdomlight@protonmail.com \
    --cc=help-guix@gnu.org \
    --cc=sirgazil@zoho.com \
    --cc=tk.code@protonmail.com \
    /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.