Parts 2 and 3 to follow in the next few weeks (will post under this thread).

Part 1 is about finding your software's mission and scope.

Open-source software is a vast web of inter-connected tools. When creating a new tool, your first job is to carve out its place in the web openly and from the outset. How can you approach that?

See neuroinformatics.dev/blog/trusted...

While prepping the talk, I realised there was much to say on this topic, so I've also prepared a 3-part blog post series.

You can find the overview here: neuroinformatics.dev/blog/trusted...

In this 2nd talk, I'll distil lessons learnt through my transition from academic research to research software engineering with @neuroinformatics.dev

Tune in if you've written code that solves a problem—maybe for your own analysis, maybe for your lab—and hope it can be useful to others.

The second talk is on Sunday, in the Open Research devroom @FosdemResearch.

fosdem.org/2026/schedul...

It's titled: "Trusted by design: set up your research software for community adoption".

My first talk is on Saturday, in the Bioinformatics & Computational Biology devroom.

fosdem.org/2026/schedul...

I'm presenting movement, our Python package for analysing animal motion.