VTK hackathon on May 13, 2026

Announcements
1

Hello VTK devs,

You’re invited to a VTK Hackathon on May 13, 2026, from 9:00 am to 4:00 pm EDT!

We’ll be getting together to tackle some long‑standing items, share ideas, and have some fun while improving VTK. Our main goals for the day are to:

  • Shrink the issue tracker – triage, close, or de‑duplicate old issues
  • Clean up the dashboard – fix noisy tests, stabilize flaky builds, and clear out the red
  • Review merge requests – push promising work over the finish line

Feel free to drop in and out as your schedule allows. Whether you want to pair‑program, review code, or just hang out and help triage, there’ll be something useful (and hopefully enjoyable!) for you to do.

Google Calendar
When: Wednesday, May 13, 2026, 9:00–16:00 (Time zone: America/New_York)
Google Meet joining info
Video call link: https://meet.google.com/xap-zcmi-sgf
Or dial: ‪(US) +1 240-623-1405‬ PIN: ‪830 613 353‬#
More phone numbers: https://tel.meet/xap-zcmi-sgf?pin=6386717808453

Got specific issues or merge requests you’d like us to look at? Bring them along!

Hope to see you there,
Sankhesh

3 Likes
2

Hi everyone,

Friendly reminder that our VTK Hackathon is tomorrow, May 13, 2026, from 9:00 am to 4:00 pm EDT.

All the details are in the primary post above.

Drop in whenever you can — whether to help triage issues, clean up the dashboard, or review merge requests.

Hope to see you there,
Sankhesh

3

Me and my team will be there (4 programmers total).

1 Like
4

Shared document for use during the hackathon: VTK Hackathon (May 13, 2026) - Google Docs

5

A huge thank you to everyone who participated in our May 13th VTK Hackathon! We had an incredibly productive day focused on resolving bug fixes, tackling long-standing issues, and pushing critical improvements across the codebase.

Here is a breakdown of what the team accomplished:

  • We successfully closed ~50+ issues! This included critical bug fixes for Thread-Safety, Serialization, and segmentation faults (such as vtkCutter segfaulting with polyhedron cells).
  • ~40+ issues were labeled with triage classification tags, helping us better organize the backlog.
  • ~15+ new merge requests to address active issues in addition to addressing the already open ones.

A significant portion of the event was dedicated to addressing Thread-Safety and Concurrency, particularly issues detected by ThreadSanitizer (TSan). We also made substantial bug fixes for WebAssembly (WASM) and cross-platform support, data format & I/O improvements (like supporting double precision data in the ExodusReader), and build system/compiler compatibility.

Momentum is high! We will be focusing on resolving the 25+ newly assigned issues, reviewing and merging the newly opened MRs, and continuing to track progress on the dashboard.

Special Thanks to Our Attendees: A massive shoutout to everyone who dropped in, wrote code, triaged issues, and shared their expertise: Jefferson Amstutz, Martin Bellehumeur, Benjamin, Ben Boeckel, Alexandru Ciobanu, Paul Elliott, Berk Geveci, Shreeraj Jadhav, Sankhesh Jhaveri, Sebastien Jourdain, Sean McBride, Corentin Munoz, Seun Odutola, Jaswant Panchumarti, Cory Quammen, and Spiros Tsalikis. Your time and effort made this event a success!

Thanks again to everyone who contributed to making VTK better!

2 Likes