# 2026.03.10 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2026-03-10-weekly-meeting/46418>\
**Category:** Weekly meetings\
**Created:** [March 9, 2026, 8:13pm UTC](https://discourse.slicer.org/t/2026-03-10-weekly-meeting/46418 "2026-03-09T20:13:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [March 9, 2026, 8:13pm UTC](https://discourse.slicer.org/t/2026-03-10-weekly-meeting/46418/1 "2026-03-09T20:13:25Z")

</div>

Tomorrow, we will be having our next weekly hangout at **10:00 AM ET until 11:00 AM ET.**

Anyone is welcome to join at this link: [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)

* * *

> **Weekly Meeting**
>
> **Starts:** March 10, 2026, 10:00am (America/New\_York)\
> **Link:** <https://bit.ly/slicer-googlemeet-hosted-by-kitware>

**Agenda:**

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

* * *

Thanks  
Sam and Ebrahim

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 9, 2026, 8:15pm UTC](https://discourse.slicer.org/t/2026-03-10-weekly-meeting/46418/2 "2026-03-09T20:15:48Z")

</div>

Tomorrow some folks from the OHIF user and developer community are planning to join the meeting so we can discuss how extensions and configurability hare handled in Slicer and OHIF.

---

<div class="post-metadata">

**Author:** ![ebrahim](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebrahim/32/13403_2.png) [@ebrahim](https://discourse.slicer.org/u/ebrahim)\
**Post date:** [March 10, 2026, 4:58pm UTC](https://discourse.slicer.org/t/2026-03-10-weekly-meeting/46418/3 "2026-03-10T16:58:17Z")

</div>

Notes from the meeting

## OHIF (Andrey, Gordon)

Looking to Slicer community for ideas about governance around an extension/module/plugin system, and how to have a rich and robust extension ecosystem. Want to see something like that in OHIF. We want to move towards OHIF having an easier and more user-friendly extension model.

## Late macOS stable extension builds (Steve, Ebrahim)

> **[SlicerStable](https://slicer.cdash.org/index.php?project=SlicerStable)**
>
> CDash is an open source, web-based software testing server. CDash aggregates, analyzes, and displays the
> results of software testing processes submitted from clients located around the world. CDash is a part of a
> ...

Stable extension comes last in the building order, so if there are a lot of delays and timeouts then it can be missed on some days. The key to see if that’s what is happening to look at how many timeouts there are on the dashboard.

### SlicerDMRI macOS issue

SlicerDMRI macOS (but not linux) build fails on stable (but not preview).

Something has rotted inside the stable build, so we should take a chance to redo the stable build on macOS when computron isn’t doing anything else.

## AI disclosure in discourse posts (Ebrahim)

> **[GitHub - ebrahimebrahim/discourse-ai-content-disclosure: A Discourse theme component that nudges users to...](https://github.com/ebrahimebrahim/discourse-ai-content-disclosure)**
>
> A Discourse theme component that nudges users to disclose AI-generated content when pasting text.

## PR on DICOM support rule in extension metadata (Andrey, Kyle)

> <https://github.com/Slicer/ExtensionsIndex/pull/2320>
>
> Add dicom\_support\_rule field to extension catalog entries to enable DICOM-aware …extension filtering and automatic extension activation.
> 
> Schema changes:
> \* Add dicom\_support\_rule field to extension catalog schema v1.0.1
> \* Field contains rule engine expression for DICOM data matching
> \* Uses Python rule-engine syntax for flexible DICOM tag comparisons
> 
> Extension updates with DICOM support rules:
> \* PETDICOMExtension: PT and RWVM modality support
> \* QuantitativeReporting: SEG, parametric maps, and SR support
> \* SlicerHeart: Cardiac ultrasound (Philips DICOM private format)
> \* SlicerRT: Radiotherapy modalities (RTDOSE, RTSTRUCT, RTPLAN, RTIMAGE)
> 
> This enables Slicer to automatically suggest or activate relevant extensions when opening DICOM data matching the specified rules.

CI fail on this is not a serious thing. Seems pretty much ready to go.

## slicer-core (Thibault)

A big milestone has been reached into making the Slicer core libraries available on PyPI.  
A preview version has been pushed to PyPI for Slicer version 5.11.0.2 and is compatible with Windows / Linux & MacOS for Python version 3.10 up to 3.13.

In the next weeks, we will work on:

- Having the SlicerCore-SDK available to create extensions compatible with SlicerCore
- Update the SlicerLayerDM extension to be available on PyPI (required by trame-slicer)
- Update trame-slicer to be compatible with the PyPI versions of SlicerCore and SlicerLayerDM
- Documenting the SlicerCore project, how to extend it and more

> **[slicer-core](https://pypi.org/project/slicer-core/)**
>
> 3DSlicer Core libraries as a python standalone project

> **[GitHub - KitwareMedical/SlicerCore](https://github.com/KitwareMedical/SlicerCore)**
>
> Contribute to KitwareMedical/SlicerCore development by creating an account on GitHub.