From: Peter Polidoro <peter@polidoro.io>
To: guix-science@gnu.org
Subject: Re: Hackatathon: 27th June! Let redo ReScience C.
Date: Thu, 18 May 2023 13:15:30 -0400 [thread overview]
Message-ID: <875y8po7zc.fsf@polidoro.io> (raw)
In-Reply-To: <mailman.135.1684425636.22153.guix-science@gnu.org>
> From: "Etienne B. Roesch" <etienne.roesch@gmail.com>
> I am also a plain old researcher in neuroscience, albeit with
> formal training in software engineering.
Just out of curiousity, do you know of other neuroscientists using
Guix or are you one of the few?
I also work with neuroscientists and have been telling them about
Guix for a couple of years now, but I have not yet been able to
convince any to even try it.
They often complain about problems they have, like struggling to
package polyglot software, that Guix could solve for them, but
seem reluctant, perhaps because of fear of lisp or not being able
to run natively on their operating system or because it is so
different than what they know.
> As such I think I would find it
> more valuable to spend time figuring out the best way to
> describe "a best
> practice" for people like me, onboarding newcomers, and write
> documentation, rather than figuring out why a Makefile doesn't
> compile and
> computer says no.
Such a "best practice" would be very valuable and I would be
interested in helping if possible.
next parent reply other threads:[~2023-05-18 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.135.1684425636.22153.guix-science@gnu.org>
2023-05-18 17:15 ` Peter Polidoro [this message]
2023-05-12 13:51 Hackatathon: 27th June! Let redo ReScience C Simon TOURNIER
2023-05-17 17:10 ` Etienne B. Roesch
2023-05-24 13:31 ` Ludovic Courtès
2023-05-25 10:08 ` Etienne B. Roesch
2023-05-25 12:19 ` Konrad Hinsen
2023-05-25 12:31 ` Etienne B. Roesch
2023-05-25 12:40 ` Konrad Hinsen
2023-05-31 10:32 ` Simon Tournier
2023-05-31 17:14 ` Etienne B. Roesch
2023-06-26 16:05 ` Simon TOURNIER
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=875y8po7zc.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=guix-science@gnu.org \
/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.
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).