From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>, help-guix@gnu.org
Subject: Re: How to present Guix to a wider audience
Date: Wed, 15 Jan 2020 09:52:15 +0100 [thread overview]
Message-ID: <87k15tw18g.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87y2u98tv1.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Hi Vagrant!
Vagrant Cascadian <vagrant@reproducible-builds.org> writes:
> Thanks, it's a nice read!
Thanks!
> How about "often difficult" instead?
Agreed and applied.
>> - Separate multi-user application collections: on a multi-user system, every
>> user can install their favourite applications independently. Applications
>> don't "pollute" the other user sessions.
>
> I wonder if most people even undertsand the concept of a multi-user
> system all that well? might be worth leaving out to keep the talking
> points short...
True, it's less fashionable these days now that everyone has their
personal machine. I'll comment it out.
>> * Can everyone use Guix?
> ...
>> More work needs to be done in terms of accessibility and easy of use so that the
>> less technically-minded among us can also enjoy Guix some day. Then, hopefully,
>> we will find Guix preinstalled on computers, ready for everyone to use.
>
> "easy of use" -> "ease of use"
Fixed.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-15 8:52 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 [this message]
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
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=87k15tw18g.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=vagrant@reproducible-builds.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 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.