unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Re: Communication and Design at Guix
Date: Thu, 17 Jan 2019 15:08:11 +0100	[thread overview]
Message-ID: <eabfca8e-4db3-387c-c6a9-e9eead38ef47@riseup.net> (raw)
In-Reply-To: <87imynh73z.fsf@elephly.net>

On 2019-01-17 12:10, Ricardo Wurmus wrote:
> 
> L p R n d n <guix@lprndn.info> writes:
> 
>> Guix is ...
>>
>> ... a package and system manager. (A seen previously, system manager is
>> too wide)
>> ... a package manager and machine administrator.
>> ... a package and machine administrator.
>> ... a package and environment manager.
>>
>> WDYT? If anyone has an idea, don't be shy :)
> 
> “administrator” is generally understood to be a person (as in “system
> administrator”).  “environment manager” is just as vague as “system
> manager”, in my opinion — “everything is the environment!”.  It only
> makes sense to people who are already familiar with the term
> “environment” in a computing context.
> 
> That’s the advantage the word “package manager” has — it’s already a
> well-established term, for better or worse.
> 
>> I'd like to keep the "package manager" part as it'll probably ring a
>> bell to any linux user and helps understand the not so familiar part
>> (system/environment dealing).
> 
> Right, that’s what I meant.
> We are underselling Guix, though, if we keep referring to it as a
> “package manager”, because people’s familiarity with other package
> managers may make them think in smaller terms.
> 
> FWIW, I’m with Ludo here with regards to “Guix” as the “single brand”.
> I disagree with this part that George wrote:
> 
>> "Guix System" is a "bad" name for "GuixSD." Why? Because a new user's
>> first expectation is for "Guix system" to refer to the whole of Guix,
>> which we want to call "Guix" (referred to as "Guix Brand" below).
> 
> In my experience “… system” is not generally used to describe a tool’s
> full set of features.  I think “Guix System” is just the right term for
> everything that Guix generates or operates on with the “guix system” set
> of commands.  “GuixOS” is, in my opinion, a pretty terrible name (I’m
> also not a fan of all the other “…OS” names out there) and it needlessly
> keeps the confusion between “Guix, the tool” and “Guix, the system”
> alive.

Interesting.

So if we go with "Guix System" would the following sentences be meaningful?

"Is your operating system running Guix?" (ambiguous)

"Which operating system do you use? Guix System."
"Are you on Guix System?"
"Which version of Guix System are you using?" (we should really have 
something like lsb_release -a output this term)
"How did you install your Guix System?"
"Can I dual-boot Guix System and Parabola GNU/Linux?"

"A: My Guix System runs Linux. B: Oh, I use the Hurd on mine!"
"I love the R.M. Stallman picture that is on my Guix System during 
boot!" :D (https://wallup.net/wallpapers/richard-stallman/)

"My Guix System performs really well"
"Since I switched my operating system to Guix System I have not looked back"
"I love my Guix System!"
"Guix helps me get things done instead of losing myself in the details 
of dependencies and stuff when coding"
"Guix makes it easy for me to sandbox my browser so I can surf without 
worrying too much"
"Guix System boots a little slower than XX but it is worth the wait!"
"I really like the roll-back provided by Guix System when I end up in a 
broken state" (geek version)
"I really like the roll-back provided by Guix System when my pc won't 
boot and just goes black so I can't use the mouse or log in." (non-geek 
version)
"I recommend Guix System because it makes it easy to copy your friends 
OS setup so that you can get to all the fun parts quickly without 
worrying about installing this or that - everything is there 
out-of-the-box!".

If not please comment.

-- 
Cheers Swedebugia

  reply	other threads:[~2019-01-17 14:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09  6:11   ` swedebugia
2019-01-09 21:45     ` Ludovic Courtès
2019-01-10 12:09       ` L p R n d n
2019-01-10 13:20         ` swedebugia
2019-01-10 14:34         ` Ricardo Wurmus
2019-01-13 21:45           ` Ludovic Courtès
2019-01-14 15:02             ` L p R n d n
2019-01-15 10:36               ` zimoun
2019-01-15 18:03                 ` nly
2019-01-15 22:08                   ` Ricardo Wurmus
2019-01-16 11:00                     ` Giovanni Biscuolo
2019-01-15 22:28               ` Ludovic Courtès
2019-01-14 23:25             ` swedebugia
2019-01-15 13:56               ` Ricardo Wurmus
2019-01-15 17:39                 ` Julien Lepiller
2019-01-15 22:30                   ` Ludovic Courtès
2019-01-10 12:17     ` L p R n d n
2019-01-10 12:57   ` L p R n d n
2019-01-10 14:30     ` Ricardo Wurmus
2019-01-13 21:50     ` Ludovic Courtès
2019-01-14 14:36       ` L p R n d n
2019-01-15 22:31         ` Ludovic Courtès
2019-01-16 16:31       ` George Clemmer
2019-01-17  0:10         ` swedebugia
2019-01-17 10:58         ` L p R n d n
2019-01-17 11:10           ` Ricardo Wurmus
2019-01-17 14:08             ` swedebugia [this message]
2019-01-17 16:24               ` L p R n d n

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eabfca8e-4db3-387c-c6a9-e9eead38ef47@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).