unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Cook, Malcolm" <MEC@stowers.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
	"myglc2@gmail.com" <myglc2@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	sirgazil <lizagris@protonmail.com>
Subject: RE: website: say what Guix is at the very top
Date: Mon, 29 Jan 2018 21:31:27 +0000	[thread overview]
Message-ID: <CY4PR2001MB1064FA7A07E439E20C3AD2BBBEE50@CY4PR2001MB1064.namprd20.prod.outlook.com> (raw)
In-Reply-To: <20180129073718.GA32294@thebird.nl>

Pjotr, that was excellently put!

I entirely agree that with the right educational materials you are going to see have the possibility of appealing to other groups/cultures/biases.

Having a section for each of the 2**3 type of user might be the perfect compromise.

Perhaps try to appeal to each audience not with "the first foo to bar" language, but rather the language of use cases, such as:

	As an administrator of a general purpose HPC cluster, I can focus on networking optimizations ("the last mile", I/O, CUDA, performance, permissions, interesting massively parallel  etc) rather than keeping up-to-date with every last scientific application.

	Guix's garbage collection capabilities remove the guess-work from deleting "old" versions of libraries from my installation!

	As an system administrator, solving the dependency hell of end-user applications should not be my problem!  Guix puts this problem where it belongs - in the hand of application specialists.

	As an sysadmin administrator, with guix I am removed from the politics of when to update an application!

	Documenting what applications are installed used to be a separate problem from that of installing them.   With GUIX, performing the installation makes them appear in my software catalog.  No more worries about inconsistencies!

	As a user of advanced scientific applications, I am now in a position to deploy which applications I need as I see fit, and have the upstream community support to share the tooling. 

	As a bioinformatics developer, the same tools I use to install application environments can be used to deploy advanced workflows with the same level of confidence.

Does this strike a sweet spot?

~malcolm_cook@stowers.org

 > -----Original Message-----
 > From: Guix-devel [mailto:guix-devel-bounces+mec=stowers.org@gnu.org]
 > On Behalf Of Pjotr Prins
 > Sent: Monday, January 29, 2018 1:37 AM
 > To: myglc2@gmail.com
 > Cc: guix-devel@gnu.org; sirgazil <lizagris@protonmail.com>
 > Subject: Re: website: say what Guix is at the very top
 > 
 > 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.
 > 
 > I have a suspicion that we are inclined as hackers to go by merit.
 > I.e., Guix is superior so we'll win. History has proven this is
 > usually not the right stance.
 > 
 > I am happy George wants to address this. I think we should be fully
 > receptive.
 > 
 > Maybe we should add new pages:
 > 
 > 1. Guix for sysadmins and devops
 > 2. Guix for end users and organisations
 > 
 > And take them by the hand.
 > 
 > Pj.
 > 
 > --


  reply	other threads:[~2018-01-29 21:31 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 [this message]
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=CY4PR2001MB1064FA7A07E439E20C3AD2BBBEE50@CY4PR2001MB1064.namprd20.prod.outlook.com \
    --to=mec@stowers.org \
    --cc=guix-devel@gnu.org \
    --cc=lizagris@protonmail.com \
    --cc=myglc2@gmail.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).