all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: myglc2@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: website: say what Guix is at the very top
Date: Fri, 16 Mar 2018 08:14:47 +0100	[thread overview]
Message-ID: <20180316071447.GA28748@thebird.nl> (raw)
In-Reply-To: <867es94zfj.fsf@gmail.com>

On Mon, Jan 22, 2018 at 11:43:12AM -0500, myglc2@gmail.com wrote:
> Agreed. The first step: STOP calling Guix a "package manager".  Why?
> Users aren't shopping for a package manager. They either already have
> one, or expect one to come with the software they are looking for.  They
> will think, "I don't need one."
> 
> So calling Guix a "package manager" sets up a marketing problem like
> selling transmissions to car drivers :-(
> 
> How can we avoid this?  Call it something else!  What?
> 
> Ricardo called Guix a "software environment manager". This is a better
> term and we can apply it to both Guix and GuixSD ;-)

I am dealing with things like

  https://github.com/openjournals/joss-reviews/issues/583#issuecomment-373621538

As the scope of the packages is much larger (in terms of #
deployments) than GuixSD I think we should take a really hard look at
how we present Guix to newcomers. That is what the front page should
address.

Maybe we should make a strong shift towards running Guix in
containers. Or create a website that treats that topic individually.
See it as a marketing gimmick.

Container use is growing rapidly and allows for leaving bare metal.
There are even routers running containers today! Containers are also
building blocks for pipelines, that is going to be huge. See, for
example the PDF at

  https://grants.nih.gov/grants/rfi/NIH-Strategic-Plan-for-Data-Science.pdf

Guix is a step up from everything else when it comes to containers.
And now we can even run GuixSD in a container ;)

Pj.

  reply	other threads:[~2018-03-16  7:19 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=20180316071447.GA28748@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --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 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.