# 2026.02.24 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266>\
**Category:** Weekly meetings\
**Created:** [February 23, 2026, 9:14pm UTC](https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266 "2026-02-23T21:14:36Z")\
**Posts on this page:** 4\
**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:** [February 23, 2026, 9:14pm UTC](https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266/1 "2026-02-23T21:14:36Z")

</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:** February 24, 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:** [February 23, 2026, 10:19pm UTC](https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266/2 "2026-02-23T22:19:16Z")

</div>

I’d like to have a follow up discussion of the [slicer-skill](https://github.com/pieper/slicer-skill) stuff.

---

<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:** [February 24, 2026, 2:02pm UTC](https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266/3 "2026-02-24T14:02:55Z")

</div>

I’d like to ask about [Improve python package installation utilities by ebrahimebrahim · Pull Request #9010 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/pull/9010) to see see if the naming `slicer.pydeps` is agreeable.

---

<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:** [February 24, 2026, 5:33pm UTC](https://discourse.slicer.org/t/2026-02-24-weekly-meeting/46266/4 "2026-02-24T17:33:52Z")

</div>

Notes from the meeting

## slicer-skill (Steve, and everyone)

- [New slicer-skill ai tool](https://discourse.slicer.org/t/new-slicer-skill-ai-tool/46243)
- [GitHub - pieper/slicer-skill: SKILLS.md style information for slicer programing and usage](https://github.com/pieper/slicer-skill)

Lots of discussion on skills and other coding agent workflows.

## pip\_install features PR (Ebrahim)

- [Slicer#9010](https://github.com/Slicer/Slicer/pull/9010)
- Docstrings shortened; most examples are moved to a [new script repository section](https://slicer--9010.org.readthedocs.build/en/9010/developer_guide/script_repository.html#python-package-management).
- Split off the `slicer.util.pip_*` out of `slicer.util` into a new package.
  - With the name `slicer.packaging` we run into a name conflict with the `packaging` module (a dependency of `pip`).
  - Landed on the name: `slicer.pydeps`. So `slicer.pydeps.pip_ensure(...)`, etc.
    - `py` in the name of a python module is kind of annoying. Or is it? pydicom?
    - Maybe we should actually make `slicer.util` into an import package and make `slicer.util.pydeps` (with a better name than `pydeps`). Because we are importing all `slicer.*` things, and so if “sub-utilities” are all direclty under the `slicer` package then we prevent ourselves from using good package names due to this name shadowing issue. We may want to set the precedent now that “sub-utilities” should be `slicer.util.*`.
    - Review can proceed and when we finalize the naming and package organization we can do it at the end before merging.