Do you run or participate in a code club at your institution, or are you interested in starting one but don’t know where to begin? @cecibaldoni.bsky.social and I are leading an ‘unconference’ discussion at @sortee.bsky.social’s virtual conference on October 16 - come share some tips and ideas!

Very excited to be travelling to Melbourne to speak at WOMBAT2025 about community building & code review. Really looking forward to reconnecting with old friends and new. 🙌

Our latest #SORTEE-led paper is out now in #ProcB!

We reviewed data/code-sharing policy clarity, strictness & timing across 275 EcoEvo journals

We also worked with #ProcB & #EcologyLetters to assess initial compliance with sharing mandates. Huge team effort! 👉 doi.org/10.1098/rspb...

🙌 wonderful work leading this @asanchez-tojar.bsky.social, @eivimeycook.bsky.social, and @nickmoran-sci.bsky.social.

Transparency with open data and code sharing is a critical first step in the quality control pipeline for research code.

very excited to be joining the Research Software Asia Australia conference this week #RSAA25

Speaking tomorrow "Piloting peer code review in a research consortium community of practice". Happy to be meeting with like minds 🥳

My lab @mpi-muenster.bsky.social is looking for a computational biologist with a passion for imaging and spatial biology. A staff scientist position with long-term perspective! Apply and spread the word 🙏 jobs.mpi-muenster.mpg.de/jobposting/0...

A couple throwback pics from past scientific lives courtesy of downloading my twitter archive ~

PhD swamp life 👩‍🎓🌱, and a classic from spotlighting for ringtail possums with Nick Golding, who I still have the pleasure of working with today 🤩

We’re excited to announce the International Research Software Conference (IRSC)!

7–8 September 2026 | Sheffield, UK & online | Co-located with #RSECon26 @society-rse.org

Learn more: www.researchsoft.org/irsc/

For updates, join: preview.mailerlite.io/forms/778129...

Image by @danielskatz.org

4/ lastly, ropensci's very own pkgcheck action.

This one is really interesting as it gives you a summary of points you've either hit or missed and summarises them in a new issue in your repo. Subsequent pushes show up as comments in the same issue thread.

docs.ropensci.org/pkgcheck/ind...

3/ pkgdown workflow

Not related to the ropensci submission, but very handy if you have a pkgdown website.

I adapted from the examples here github.com/r-lib/action.... It is great knowing the website is up to date with changes I've pushed and I didn't have to separately re-publish the website.

2/ I also set up an action to access my code coverage and report it on the readme. It's not as high as I'd like yet, but it's getting there!

To get this to work I first had to link the repo on codecov.io.

github.com/codecov/code...

1/ continuous integration

Compared to the last time I set up continuous integration, things are SO EASY now. I used the following:

github.com/r-lib/action...

Going to start a series of threads on what I've been learning as I get an #rstats 📦 ready to submit to @ropensci.org.

Every time I think the package is "ready" I find another checklist I haven't been through, but it's making it all the better.

This first thread is on github actions!

Stopped using "X" years ago and have finally made a switch. Hope to reconnect with folks and touch back in to the social land to share and talk about open science, research software, ecology, and public health. 🙌