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 13:11:23 -0500	[thread overview]
Message-ID: <86607h7vas.fsf@gmail.com> (raw)
In-Reply-To: <20180131172717.GA17794@thebird.nl> (Pjotr Prins's message of "Wed, 31 Jan 2018 18:27:17 +0100")

On 01/31/2018 at 18:27 Pjotr Prins writes:

> On Wed, Jan 31, 2018 at 11:58:09AM -0500, myglc2@gmail.com wrote:
>> 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 
>
> I doubt they will use GuixSD unless they have a very specific purpose
> in mind, e.g., say for mailserver deployment. Cloud/VMs. It could
> work, but I don't think it is a large group we can pitch to.

What about a forward-thinking sysadmin commissioning new systems for a
startup? If they know they want Guix is there a reason they wouldn't
install GuixSD?

>
>> | user/developer/researcher   | x    |        | productivity tool
>
> This is my favorite because they are potential packagers.
>
>> | generic organizational user | ?    |        | ?                                    |
>
> Yes, another target group, i.e., the pointy haired boss. Some of these
> understand the concept of reducing cost.

Here I am thinking of "unsophisticated" users, e.g., someone told to run
SAS on a server that is probably not going to actually ever call guix.

>
>> | desktop distro user         |      | ?      | ?                                    |
>
> Libre desktop user. Yes.
>
>> |-----------------------------+------+--------+--------------------------------------|
>
> We also have embedded systems and phones as a potential audience. I
> think OpenWRT/LEDE, for example, could buy into Guix. And then there
> is Android. If we are able to strip down packages to a minimum that
> becomes very interesting to them.

OK, so like this ?

>> | Target Group                | Guix | GuixSD | 
>> | embedded sys/phone          |      | x      |

>
> Then we have HPC as a specialization with optimized targets and
> relocatable packages.

OK, so like this?

>> | Target Group                | Guix | GuixSD | 
>> | HPC sysadmin                | x    | x      | optimized targets and relocatable packages
>
> And light containers for webservice/cloud deployments...

Is this more detail on HPC or something else entirely?

TIA - George

  reply	other threads:[~2018-01-31 18:11 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 [this message]
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=86607h7vas.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).