# 2026.07.14 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579>\
**Category:** Weekly meetings\
**Created:** [July 8, 2026, 11:13am UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579 "2026-07-08T11:13:38Z")\
**Posts on this page:** 13\
**Page:** 1

<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:** [July 8, 2026, 11:13am UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/1 "2026-07-08T11:13:39Z")

</div>

Title: 2026.07.14 Weekly Meeting

Next Tuesday, 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: [Google Meet meeting](https://meet.google.com/ymg-ahrz-www)

* * *

> **Weekly Meeting**
>
> **Starts:** July 14, 2026, 10:00am (America/New\_York)\
> **Link:** <https://meet.google.com/ymg-ahrz-www>

**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:** ![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:** [July 13, 2026, 1:06pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/2 "2026-07-13T13:06:15Z")

</div>

Let’s include discussing what is still wrong with the macOS extension packages after the 5.12.1 patch release: [Slicer 5.12: Summary, Highlights, and Changelog - #6 by muratmaga](https://discourse.slicer.org/t/slicer-5-12-summary-highlights-and-changelog/47540/6)

---

<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:** [July 13, 2026, 7:41pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/3 "2026-07-13T19:41:07Z")

</div>

We could discuss default mouse modes and how to make the mouse modes more discoverable in the first place.

See [ENH: Add Scroll mouse mode to browse slices by click-and-drag by lassoan · Pull Request #9284 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/pull/9284)

---

<div class="post-metadata">

**Author:** ![RafaelPalomar](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rafaelpalomar/32/1436_2.png) [@RafaelPalomar](https://discourse.slicer.org/u/RafaelPalomar)\
**Post date:** [July 14, 2026, 8:31am UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/4 "2026-07-14T08:31:54Z")

</div>

Discussion on the following two PRs, which require some actions to be fully valid:

- [BUG: Name VTK regex version-script node to fix vtktiff link (#9252) by RafaelPalomar · Pull Request #9286 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/pull/9286)
- [ENH: Adapt qRestAPI consumption to the modernized CMake package by RafaelPalomar · Pull Request #9287 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/pull/9287)

Actions:

- Merge changes in [ENH: Modernize CMake packaging to match vtkAddon (supersedes #27) by RafaelPalomar · Pull Request #28 · commontk/qRestAPI · GitHub](https://github.com/commontk/qRestAPI/pull/28)
- Rebuild the docker images for the CI to have the right base

---

<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:** [July 14, 2026, 3:53pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/5 "2026-07-14T15:53:32Z")

</div>

Notes from today’s meeting:

## Agenda

- [Is something still wrong with macOS extnesion packages?](https://discourse.slicer.org/t/slicer-5-12-summary-highlights-and-changelog/47540/6)
- [Rafael PRs that need discussion/actions](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/4)
- [Default mouse mode and mouse mode discoverability](https://github.com/Slicer/Slicer/pull/9284)

## Install script

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

Mauro adding to Slicer/Utilities in a PR

After review and testing and agreement, we can make [slicer.org/install.sh](http://slicer.org/install.sh) redirect to it on github.

Still need someone to test on macOS:

```auto
curl -fsSL https://raw.githubusercontent.com/mauigna06/slicer-installer/main/install.sh | sh

```

And here is how to try it out on windows right now:

```auto
powershell -c "irm https://raw.githubusercontent.com/mauigna06/slicer-installer/main/install.ps1 | iex"

```

Consider:

- a no-interaction mode, for people who want to use the script in automations
- an automatic dependency installation mode, for people who want to use the script to create docker images
- the possibility of packaging an installer script into the tarball, in the linux case
- representing system dependencies in a separate file that the script references and that the docs can also reference to report system dependencies, so that they are in one place and never go out of sync

## macOS stable extension issues

Signs point to a stale state during our attempt to do an incremental rebuild on the macOS factory machine. Ebrahim will disable nightly and do a completely clean rebuild of both SLicer and extensions on the macOS factory machine. This will have to be called 5.12.2 even though there might not be any actual changes, so that there is not a chance of confusing two different 5.12.1 packages. Planning to kick this off tomorrow.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 16, 2026, 12:34am UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/7 "2026-07-16T00:34:24Z")

</div>

Here is the checklist for the Slicer-5.12.2 patch release:

> <https://github.com/Slicer/Slicer/issues/9288>
>
> Checklist \*\*Installers Release\*\*:
> 
> \* \[x\] \[Pin\](https://docs.github.com/en/enterp…rise-cloud@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository) this issue.
> \* \[x\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-release-in-progress-post) the \`Release in progress\` post.
> \* \[x\] \[Disable\](https://github.com/Slicer/Slicer/wiki/Release-Process#enable-or-disable-regular-nightly-builds) regular nightly builds.
> \* \[x\] \`CMakeLists.txt\`: \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#cmakeliststxt-update-the-slicer-version-information-for-the-release) the Slicer version information for the release.
> \* \[x\] \[Tag\](https://github.com/Slicer/Slicer/wiki/Release-Process#tag-the-repository) the repository with \`v5.12.2\`.
> \* \[x\] \[Create\](https://github.com/Slicer/Slicer/wiki/Release-Process#create-release-or-patch-release-on-slicer-packageskitwarecom) release \`5.12.2\` on \[slicer-packages.kitware.com\](https://slicer-packages.kitware.com/#folder/5f4474d0e1d8c75dfc705482).
> \* \[x\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-release-scripts) release scripts.
> \* \[\] \[Generate\](https://github.com/Slicer/Slicer/wiki/Release-Process#generate-application-and-extension-packages) application and extension packages. See https://slicer.cdash.org/index.php?project=SlicerStable&date=2026-07-15.
> \* Linux: ✔️ 
> \* macOS: ⏳
> \* Windows: ✔️ 
> \* \[x\] Update \[Release Details\](https://github.com/Slicer/Slicer/wiki/Release-Details) on the Slicer GitHub wiki.
> 
> \--------------------------------------
> 
> Checklist \*\*Post Release\*\*:
> 
> \_These steps will take place in the week following \*\*Installers Release\*\* steps\_
> 
> \* \[\] \[Re-enable\](https://github.com/Slicer/Slicer/wiki/Release-Process#enable-or-disable-regular-nightly-builds) regular nightly builds.
> \* \[\] Manually \[sign the packages\](https://github.com/Slicer/Slicer/wiki/Signing-Application-Packages).
> \* Linux: NA
> \* macOS: signed :question:, notarized :question:
> \* Windows: ✔️
> \* \[\] \[Upload\](https://github.com/Slicer/Slicer/wiki/Release-Process#upload-signed-release-packages) signed release packages in the release folder.
> \* Linux: NA
> \* macOS: :question:
> \* Windows: ✔️
> \* \[\] In the \`5.12.2\` release folder, update each \`Slicer\_\<os\>\_\<arch\>\_\<revision\>\` items changing the \`pre\_release\` metadata from \`true\` to \`false\`.
> \* Linux: ✔️ 
> \* macOS: :question:
> \* Windows: ✔️
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-extensionstats-module) \`ExtensionStats\` module. (just merge \[this\](https://github.com/Slicer/SlicerDeveloperToolsForExtensions/pull/37))
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-external-websites) external websites.
> \* ~~\[\] \[Generate release notes\](https://github.com/Slicer/Slicer/wiki/Generating-Release-Notes) and prepare Discourse content.~~
> \* ~~\[\] Finalize Slicer Announcement and release notes in HackMD (or equivalent shared document).~~
> \* \[\] Publish Slicer Announcement & release notes on Discourse.
> \* \[\] Unpin this issue.

---

<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:** [July 16, 2026, 12:10pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/8 "2026-07-16T12:10:02Z")

</div>

@muratmaga Hopefully 5.12.2 does not have the extensions issue on macOS, but I have not tried it. Please let us know if, when you try it, the same issue still occurs. Our testing strongly suggested that a clean re-build should fix things but there was not certainty.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [July 16, 2026, 2:02pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/9 "2026-07-16T14:02:34Z")

</div>

@ebrahim I observed errors upon launching Slicer 5.12.2 with the MarkupsToModel extension with the message appearing to mention “relative path not allowed in hardened program” where the hardened program is likely tied to the fact that Slicer stable releases (unlike Preview builds) are codesigned and notarized. I’m using macOS Tahoe for reference here.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/d/4d4e9f56a962445eec58252d47e998baca23acb8.png)

---

<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:** [July 16, 2026, 3:47pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/10 "2026-07-16T15:47:39Z")

</div>

Hmm. I guess we have a legitimate bug here that [COMP: Update DCMTKcs to fix OpenJPEG over-linking on macOS by lassoan · Pull Request #9263 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/pull/9263) solved for preview builds but there remains an issue with signed macOS packages. So it was not just a stale build environment after all.

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [July 17, 2026, 3:58pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/11 "2026-07-17T15:58:10Z")

</div>

So will there be a then 5.12.3 for this fix then? Because right now none of the C++ extensions work properly as far as I can tell.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 17, 2026, 4:02pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/12 "2026-07-17T16:02:53Z")

</div>

Yes, of course, we’ll need a release that works well.

---

<div class="post-metadata">

**Author:** ![mau\_igna\_06](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mau_igna_06/32/9056_2.png) [@mau\_igna\_06](https://discourse.slicer.org/u/mau_igna_06)\
**Post date:** [July 17, 2026, 5:34pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/13 "2026-07-17T17:34:34Z")

</div>

> 🤖 This post was written with AI assistance.

A few governance questions I cannot answer myself:

> [@ebrahim](#):
>
> - a no-interaction mode, for people who want to use the script in automations

1. **When the target version is already installed and you haven’t set `SLICER_IF_EXISTING` env variable, what should a no-interaction run do: reinstall it (today’s no-terminal behavior) or exit 0 without touching it?** This is the idempotency question — it decides whether repeated automation runs re-download ~1 GB or become no-ops.
2. **Do you also need quiet output (no logo, no progress bar) for logs, or is suppressing prompts enough?** _(default: prompts only — logo and progress bars are already suppressed when output isn’t a terminal)_
3. **Linux/macOS only, or do you automate the Windows installer too?**

> [@ebrahim](#):
>
> - an automatic dependency installation mode, for people who want to use the script to create docker images

1. **If installing dependencies fails, should the whole install fail (good for `RUN` steps in a Dockerfile) or warn and continue?**
2. **If the script is _not_ root, should it attempt `sudo` (which may password-prompt — colliding with no-interaction mode) or refuse and print the command as it does today?**
3. **Do you run Slicer headless in the container (e.g. `xvfb-run Slicer --no-main-window`)?** If so, should the mode optionally install headless extras like `xvfb`, or stay strictly at Slicer’s runtime library list?

> [@ebrahim](#):
>
> - the possibility of packaging an installer script into the tarball, in the linux case

1. **Who is it for: people who manually download the tarball from [download.slicer.org](http://download.slicer.org) and want the wiring (launcher symlink, menu entry, deps hint) afterwards, or is the goal to get upstream Slicer packaging to bundle the script officially?**
2. **When run from an extracted tree, should it wire that tree up in place (wherever it was extracted), move it to the standard `~/.local/opt` location, or ask?**
3. **Should it be the same `install.sh` gaining an offline/local mode (one file, could be dropped into the tarball as-is), or a separate minimal script that contains only the wiring logic?**
4. **Must it work fully offline (no checksum/version lookups at all)?**
5. **Should it also offer uninstall of that copy?** _(default: yes — the uninstall logic already exists in `uninstall_linux`)_

> [@ebrahim](#):
>
> - representing system dependencies in a separate file that the script references and that the docs can also reference to report system dependencies, so that they are in one place and never go out of sync

1. **Who consumes the file besides this repo’s README — e.g. the official Slicer docs or a Discourse post wanting a stable URL?** Decides whether the file format/location becomes a public contract.
2. **Plain text lists per package manager (`deps/apt.txt`, `deps/dnf.txt`, `deps/pacman.txt`) or something structured (JSON/YAML) for machine consumption?**
3. **Is a repo-internal sync acceptable — the lists get embedded into `install.sh` by a generator, with a CI check that fails on drift — or do you want the script to fetch the file at runtime so even old script copies stay current?** Runtime fetching adds a network failure mode to `curl | sh`; embedding keeps the script self-contained.
4. **Should the file format express conditionals (e.g. `libasound2t64` vs `libasound2` depending on Ubuntu release), or does that logic stay in the script with the file listing the canonical names?**

* * *

Thank you

---

<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:** [July 17, 2026, 5:38pm UTC](https://discourse.slicer.org/t/2026-07-14-weekly-meeting/47579/14 "2026-07-17T17:38:47Z")

</div>

@mau_igna_06 Thanks for making this script and working out the questions that we need to answer. Maybe a first step could be to create the draft PR with the current script and start the discussion there (copying some of these same questions there). So that way everyone can see the script and comment on it, try things out in the context of building the docs, etc.