Posted in 2026

GSoC 2026: single-channel support in cellfinder

Hi, I’m Soumya. I was one of the Neuroinformatics Unit Google Summer of Code (GSoC) interns for the 2026 summer term, and I worked on broadening the range of inputs cellfinder accepts, in both channel count and dimensionality.

Read more ...


GSoC 2026: Miscellaneous maintenance work on BrainGlobe overall infrastructure

Hi, I’m Varun. This summer I worked with BrainGlobe and the Neuroinformatics Unit as part of Google Summer of Code.

Auto-generated brainrender API reference page

Read more ...


A napari GUI for manual tracklet refinement in movement - Final GSoC Report

Hi, I’m Anna. I’m a neuroscientist interested in the study of social behaviour. During my PhD I started using different open-source pose estimation tools, such as DeepLabCut, to track animal behaviour. Working with real, multi-animal recordings, I kept running into the same problems: occlusions, noisy detections, and identity swaps that no automated pipeline could fully resolve. Programmatic corrections improved the data, but visual inspection and manual correction were always necessary, and the tools available for that were slow and hard to scale to large datasets.

Read more ...


Trusted by design (part 3): embrace radically open communication

Open-source software is public, yet much of the communication around it may happen in private emails, internal Slack channels and meetings with no minutes. This disconnect can erode the very trust that openness is meant to build. What if communication were radically open—a habit of constant, multi-way interactions visible to anyone who cares to look?

Read more ...


Trusted by design (part 2): release early, release often

‘Release early, release often’ is an often-repeated mantra, popularised by Eric S. Raymond in his 1997 essay “The Cathedral and the Bazaar”. I hadn’t fully grasped its significance until I switched from academic research to full-time software development. How early? How often? And why is this so critical to establishing and maintaining trust?

Read more ...


Trusted by design (part 1): define your software’s mission and scope

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

Read more ...


Trusted by design (intro): set up your research software for community adoption

So, you want to create an open-source research software package—and not just for yourself or your group. You’d like people around the world to use it, and even contribute to it. How do you persuade them it’s worth their time?

Read more ...