public inbox for ravanan@systemreboot.net
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: guix-science@gnu.org
Cc: ravanan@systemreboot.net
Subject: Talk at RSECon26 on Guix and ravanan
Date: Fri, 11 Sep 2026 23:50:59 +0100	[thread overview]
Message-ID: <87ik4bcsh8.fsf@systemreboot.net> (raw)


Hi,

I gave a talk on Guix and ravanan[1] yesterday at RSECon26[2], the Research
Software Engineering conference. My slides are at [3].

[1]: https://forge.systemreboot.net/ravanan/
[2]: https://rsecon26.society-rse.org/
[3]: https://zenodo.org/records/22682923

I have been working on ravanan for a couple of years now. ravanan is a
Common Workflow Language (CWL [4]) runner that uses Guix to provide
strong reproducibility guarantees and content-addressed caching. CWL is
a standards-based workflow language that is used in scientific
computing. You may have heard of other workflow languages such as
Nextflow, Snakemake and the Guix Workflow Language.

[4]: https://www.commonwl.org/

Based on conversations at the conference, I feel that Guix is slowly
getting on the radar of the research software engineering world. More
and more people have at least vaguely heard of Guix. Compare this with a
few years back when no one had a clue. Thanks to the community for
having carefully cultivated and cared for Guix these many years!

I also ran into Peter Schmidt from the Code for Thought[5] podcast. I
may be appearing on his podcast to talk about Guix.

[5]: https://codeforthought.buzzsprout.com/

In other ravanan news, the amazing Luis Felipe designed a logo for
ravanan. You can see it on the ravanan homepage.

Cheers!
Arun

             reply	other threads:[~2026-09-11 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 22:50 Arun Isaac [this message]
2026-09-14 13:59 ` Ludovic Courtès

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=87ik4bcsh8.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guix-science@gnu.org \
    --cc=ravanan@systemreboot.net \
    /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