unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2@gmail.com
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org, sirgazil <lizagris@protonmail.com>
Subject: Re: website: say what Guix is at the very top
Date: Wed, 31 Jan 2018 11:58:09 -0500	[thread overview]
Message-ID: <86h8r26k4e.fsf@gmail.com> (raw)
In-Reply-To: <20180129073718.GA32294@thebird.nl> (Pjotr Prins's message of "Mon, 29 Jan 2018 08:37:18 +0100")

On 01/29/2018 at 08:37 Pjotr Prins writes:

> On Sun, Jan 28, 2018 at 11:14:15PM -0500, myglc2@gmail.com wrote:
>> > I’m not a fan of sales messages and that kind of language
>> > (“introducing”, “the first foo to do bar”, etc); I also don’t like that
>> > these are all worded negatively, which is something we should avoid.
>> 
>> OK but keep in mind that we have very little time to capture a
>> prospective user's attention. You normally do this by saying what is
>> unique about a product and what problem it solves.  This is my attempt
>> at points that might convince a sysadmin and/or user to try
>> Guix/GuixSD. We can make it less salesy. But are the points wrong?  Is
>> something missing? Are there better points to make?
>
> The case is a bit complicated here. Not only do we present two
> products we also have multiple audiences. The current website (in the
> true GNU spirit) addresses hackers. That works because Guix was WIP
> and needed more of those. The hacker spirit has served us and still
> serves us.
>
> But to popularize Guix we have at least two other audiences. The first
> one 'sysadmins' and 'devops' is an important one because we need to
> get Guix on systems they control. This proves to be a hard sell in my
> experience.  Mostly, I think, because sysadmins are not aware of the
> benefits - or simply don't want to be aware. No kidding, I have
> encountered that a few times. 
>
> Then there are end-users and developers who can use Guix for their
> purposes and it would liberate them.
>
> The net benefit for all is gaining control, reproducibility and
> (hopefully) saving time.
>
> I.e., to have a successful sales pitch you'll need to address 2*3=6
> targets.

To be explicit, I added a couple target groups and indicated the product
we would pitch with an x ...

| Target Group                | Guix | GuixSD | Motivation                           |
|-----------------------------+------+--------+--------------------------------------|
| hacker                      | x    | x      | scheme, functional, free             |
| sysadmin & devop            | x    | ?      | make user/developer/researcher happy |
| user/developer/researcher   | x    |        | productivity tool                    |
| generic organizational user | ?    |        | ?                                    |
| desktop distro user         |      | ?      | ?                                    |
|-----------------------------+------+--------+--------------------------------------|

Note: "?" - not sure

WDYT? - George

  parent reply	other threads:[~2018-01-31 16:58 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
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 [this message]
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=86h8r26k4e.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=lizagris@protonmail.com \
    --cc=pjotr.public12@thebird.nl \
    /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).