unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: George myglc2 Clemmer <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: website: say what Guix is at the very top
Date: Fri, 19 Jan 2018 08:42:29 +0100	[thread overview]
Message-ID: <87efmm70re.fsf@elephly.net> (raw)
In-Reply-To: <863732wf9z.fsf@gmail.com>


Hi George,

> Our immediate challenge is that we seem to think we have at least two
> products. We need to decide if we really have multiple products and, if
> we do, how many and what they are. Then we must clearly separate them
> and make it easy for potential customers to determine which one they
> might use.

I agree.

It seems unfortunate to me that we have one shared website for GuixSD
and Guix.  As much as I love GuixSD, I think Guix is the main “product”
and GuixSD would need to be moved to a subsite.  That’s primarily
because GuixSD can be explained in terms of Guix, but explaining Guix as
“the package manager we use for GuixSD” seems less helpful.

We have many more use-cases for Guix than for GuixSD, Guix is mature and
GuixSD is still exploring ways to provide its own spin on traditional
features (e.g. “guix deploy”).

It’s much easier to tell people to “upgrade” to GuixSD when they already
know Guix as a mature, reliable, and understandable piece of software,
than to get them to “settle” for just Guix on a foreign distro, when
we’re “selling” them GuixSD.

My proposal is to keep https://gnu.org/s/guix focussed on Guix the
functional software environment manager, and have the distro under
https://gnu.org/s/guix/distro.

What do you think?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-01-19  8:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 17:30 website: say what Guix is at the very top Ricardo Wurmus
2018-01-17 18:08 ` Tobias Geerinckx-Rice
2018-01-19  8:04   ` Ricardo Wurmus
2018-01-21 17:11     ` Tobias Geerinckx-Rice
2018-01-19  6:09 ` George myglc2 Clemmer
2018-01-19  7:42   ` Ricardo Wurmus [this message]
2018-01-19 13:32     ` Ludovic Courtès
2018-01-19 20:35       ` myglc2
2018-01-21 14:47       ` Ricardo Wurmus
2018-01-24  5:54         ` myglc2
2018-01-24 14:24           ` Oleg Pykhalov
2018-01-24 14:22         ` Ludovic Courtès
2018-01-26 23:03           ` myglc2
2018-01-27 16:14             ` Ludovic Courtès
2018-01-27 18:20               ` myglc2
2018-01-27 21:59                 ` Pjotr Prins
2018-01-28 16:24                 ` Ricardo Wurmus
2018-01-29  4:14                   ` myglc2
2018-01-29  7:37                     ` Pjotr Prins
2018-01-29 21:31                       ` Cook, Malcolm
2018-01-29 22:20                         ` Ricardo Wurmus
2018-01-29 22:24                           ` Cook, Malcolm
2018-01-30  1:03                             ` Ricardo Wurmus
2018-01-30 22:17                               ` myglc2
2018-01-30  1:43                             ` George myglc2 Clemmer
2018-01-30  2:56                               ` Ricardo Wurmus
2018-01-30  7:31                           ` Pjotr Prins
2018-01-30  7:46                           ` Pjotr Prins
2018-01-31 16:58                       ` myglc2
2018-01-31 17:27                         ` Pjotr Prins
2018-01-31 18:11                           ` myglc2
2018-01-31 18:13                             ` Pjotr Prins
2018-01-28  0:35               ` Chris Marusich
2018-01-22  7:04 ` Chris Marusich
2018-01-22 16:43   ` myglc2
2018-03-16  7:14     ` Pjotr Prins
2018-01-24 14:19   ` Ludovic Courtès
2018-01-28  0:33     ` Chris Marusich
2018-01-28 21:58       ` Ludovic Courtès
2018-01-29  2:08         ` Chris Marusich

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=87efmm70re.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=myglc2@gmail.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 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).