2024.07.16 Weekly Meeting

[Sam_Horvath (Sam Horvath (Kitware))]

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

---

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

[jcfr (Jean Christophe Fillion Robin (Kitware))]

Meeting notes

• Telemetry

  • Progress toward creating the fontend
  • Will soon publish a branch onto GitHub - Slicer/slicer-usage-stats: Source code of the site allowing to visualize Slicer application and extensions usage statistics.

• CLI executable terminates with fault due to incompatible system C++ redistributable · Issue #7847 · Slicer/Slicer · GitHub

  • Evaluate if setting _DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR helps

  • If does not work, may update dashboard script to ensure specific toolset is selected.

    For example:

    dashboard_set(CTEST_CMAKE_GENERATOR_TOOLSET "v142,version=14.28")
    

  • Related discussion, see Developer Community

  • Note: Qt 6.8 will ship only for VS 2022. See Moving to Microsoft Visual C/C++ (MSVC) compiler 2022 in Qt 6.8 packages. Please test this on Qt 6.7

• https://py-free-threading.github.io/

• Extension tier support

  • Add support for extension tiers PR Slicer#7748

  • Server / Python Client: Add support for extension “tier” metadata PR girder/slicer_package_manager#124

  • To do

    • Update qSlicerExtensionsManagerWidget
    • Update web application KitwareMedical/slicer-extensions-webapp

  • We revisited the definition of tiers and updated the post accordingly.

    • Tier 5: Critically important extensions, supported by Slicer core developers
    • Tier 3: Community-supported extensions.
    • Tier 1: Experimental extensions
    

[jamesobutler (James Butler)]

@jcfr

We revisited the definition of tiers and updated the post 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:

InsightSoftwareConsortium/ITK/blob/f88a2896a7449088af0a29070e53043f85ad6a3e/Modules/Remote/README.md?plain=1#L58-L63

[jcfr (Jean Christophe Fillion Robin (Kitware))]

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”.

[jamesobutler (James Butler)]

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