From: Ricardo Wurmus <rekado@elephly.net>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"myglc2@gmail.com" <myglc2@gmail.com>,
sirgazil <lizagris@protonmail.com>
Subject: Re: website: say what Guix is at the very top
Date: Mon, 29 Jan 2018 23:20:17 +0100 [thread overview]
Message-ID: <87po5ss3xa.fsf@elephly.net> (raw)
In-Reply-To: <CY4PR2001MB1064FA7A07E439E20C3AD2BBBEE50@CY4PR2001MB1064.namprd20.prod.outlook.com>
Hi Malcolm,
> I entirely agree that with the right educational materials you are
> going to see have the possibility of appealing to other
> groups/cultures/biases.
Yes, I think that does make sense.
> 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!
(It’s “Guix”, not “GUIX”. People at work also always write “GUIX” and I
can’t figure out why… Maybe we should come up with a backronym to make
it a valid alternative spelling :))
> 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?
I like these testimonial style descriptions, and I think it makes sense
to add separate sections for different archetypical users. (We already
have a related section entitled “GuixSD and GNU Guix in your field”,
which I found intriguing, but it only links to blog posts with certain
tags.)
However, I think that this is tangential to the question of whether to
move the GuixSD description and intro to a separate page. If we added
those sections they’d be only about Guix, not about GuixSD, no?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-01-29 22:20 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 [this message]
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=87po5ss3xa.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=MEC@stowers.org \
--cc=guix-devel@gnu.org \
--cc=lizagris@protonmail.com \
--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).