From: "Cook, Malcolm" <MEC@stowers.org>
To: 'Ricardo Wurmus' <ricardo.wurmus@mdc-berlin.de>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"'bio-packaging@mailman.open-bio.org'"
<bio-packaging@mailman.open-bio.org>
Subject: RE: Making the case for GNU Guix ... advice sought
Date: Mon, 29 Feb 2016 17:10:19 +0000 [thread overview]
Message-ID: <2600e6b3751d428c8143a16cd514327d@exchsrv2.sgc.loc> (raw)
In-Reply-To: <a7d56301b77e467c88471fde35d16ede@exchsrv2.sgc.loc>
By the way, below my sig is my new and improved "wrap" to my "pitch". I hope you like it...
~Malcolm
Guix provides a well-engineered, supportable, portable, and extensible approach to software package and environment management. It allows to adopt and create unambiguous, clearly-specified, stand-alone, and reproducible software environments. It provides the administrative flexibility to deploy with transactional control a common standard suite of applications, as well as the agility to quickly respond to individual user and application requirements for more customized environments. Guix reduces the administrative burden for software package and environment management by allowing it to be distributed among researchers, with a natural means of coordination of effort. By offering a unified approach to environment management, it replaces the need for multiple other such tools, reducing support overhead. Guix can serve the needs for computational reproducibility through means of sharing these environments across a range of hosts and computer operating systems with both internal collaborators as well as the broader research community.
In short, Guix provides a rigorous response to requirements for package and environment integrity in a rapidly evolving research computing environment while easing and distributing the burden of administration.
> -----Original Message-----
> From: guix-devel-bounces+mec=stowers.org@gnu.org [mailto:guix-devel-
> bounces+mec=stowers.org@gnu.org] On Behalf Of Cook, Malcolm
> Sent: Monday, February 29, 2016 10:55 AM
> To: 'Ricardo Wurmus' <ricardo.wurmus@mdc-berlin.de>
> Cc: guix-devel@gnu.org; 'bio-packaging@mailman.open-bio.org' <bio-
> packaging@mailman.open-bio.org>
> Subject: RE: Making the case for GNU Guix ... advice sought
>
> > Cook, Malcolm <MEC@stowers.org> writes:
> >
> > > Hi Ricardo,
> > >
> > > Great specifics. If you can help me solve a few of my remaining
> > > questions, in-line below, I'd be much obliged....
> >
> > Hi Malcolm,
> >
> > I see that others have already replied to some of your questions. Are
> > there any other things that you’d like us to clarify?
> [Cook, Malcolm]
>
> No - but thanks for reaching out - I'm sure I will have more questions as I
> slowly advance.
>
> Insofar as my "MakingTheCase" document, I have finished it to my current
> satisfaction and have used it internally to communicate my perceived value of
> moving forward with GUIX.
>
> https://github.com/malcook/sce/blob/master/MakingTheCase.org
>
> Again, thank everyone for your helps. If the Guix project wanted to
> incorporate this document with whatever improvements, I'd be happy to
> contribute.... just say the word....
>
> Cheers,
>
> Malcolm
>
>
> >
> > ~~ Ricardo
next prev parent reply other threads:[~2016-02-29 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 19:43 Making the case for GNU Guix ... advice sought Cook, Malcolm
2016-02-09 15:03 ` Ricardo Wurmus
2016-02-09 19:54 ` Leo Famulari
2016-02-09 20:27 ` Ludovic Courtès
2016-02-09 20:30 ` Ludovic Courtès
2016-02-18 23:29 ` Cook, Malcolm
2016-02-19 10:10 ` Pjotr Prins
2016-02-19 15:06 ` Cook, Malcolm
2016-02-28 13:52 ` Ludovic Courtès
2016-02-28 14:42 ` Ricardo Wurmus
2016-02-29 16:55 ` Cook, Malcolm
2016-02-29 17:10 ` Cook, Malcolm [this message]
2016-03-01 21:22 ` Ludovic Courtès
2016-02-09 20:36 ` Ludovic Courtès
2016-02-10 16:01 ` Cook, Malcolm
2016-02-18 23:26 ` Cook, Malcolm
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=2600e6b3751d428c8143a16cd514327d@exchsrv2.sgc.loc \
--to=mec@stowers.org \
--cc=bio-packaging@mailman.open-bio.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.