# 2024.07.16 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386>\
**Category:** Weekly meetings\
**Created:** [July 15, 2024, 8:05pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386 "2024-07-15T20:05:07Z")\
**Posts on this page:** 5\
**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:** [July 15, 2024, 8:05pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386/1 "2024-07-15T20:05:07Z")

</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:** July 16, 2024, 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 J-Christophe

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [July 16, 2024, 6:30pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386/2 "2024-07-16T18:30:19Z")

</div>

### Meeting notes

- Telemetry

- [CLI executable terminates with fault due to incompatible system C++ redistributable · Issue #7847 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/7847)

- [https://py-free-threading.github.io/](https://py-free-threading.github.io/)

- Extension tier support

---

<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, 2024, 7:30pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386/3 "2024-07-16T19:30:38Z")

</div>

> [@jcfr](#):
>
> We revisited the definition of tiers and updated [the post](https://discourse.slicer.org/t/introduction-of-tiers-for-slicer-extensions/34870) accordingly.
> 
> - Tier 5: Critically important extensions, supported by Slicer core developers
> - Tier 3: Community-supported extensions.
> - Tier 1: Experimental extensions

@jcfr I think this change is actually more confusing. When I think of something as being “Tier 1” I think of it as being the best (top tier). Could we instead call the lowest quality extensions “Compliance Level 1 Star” and the highest quality extensions “Compliance Level 5 Star”? A higher number in this usage seems clear that it has been reviewed/scored higher. It also aligns with the terminology used by ITK for its remote modules:

> <https://github.com/InsightSoftwareConsortium/ITK/blob/f88a2896a7449088af0a29070e53043f85ad6a3e/Modules/Remote/README.md?plain=1#L58-L63>

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [July 16, 2024, 8:38pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386/4 "2024-07-16T20:38:13Z")

</div>

This change was inspired from “tier” (or “level”) also used in the context of IT support in which “tier 5” (or “level 5”) is the _best_.

How about simply renaming the `tier` metadata to `level` ?

In the extension manager UI, we would also have “Show All ” instead of “Tier 3 and above”.

---

<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, 2024, 9:23pm UTC](https://discourse.slicer.org/t/2024-07-16-weekly-meeting/37386/5 "2024-07-16T21:23:19Z")

</div>

“Level 5” to convey “best” seems good. The ITK convention seems to interchange whether the term is Level number or star number.