# 2025.07.01 Weekly Meeting

**URL:** https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561
**Category:** Weekly meetings
**Created:** [July 1, 2025, 12:46pm UTC](https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561 "2025-07-01T12:46:12Z")
**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: [July 1, 2025, 12:46pm UTC](https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561/1 "2025-07-01T12:46:12Z")

</div>

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

Anyone is welcome to join at this link: [https://bit.ly/slicer-googlemeet-hosted-by-kitware](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 2, 2025, 1:19am UTC](https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561/2 "2025-07-02T01:19:30Z")

</div>

### Meeting Notes

#### Qt6 Transition

- The transition to **Qt6** is underway, led by @jcfr.
- For progress and technical details, refer to the [Project Week 43 notes](https://projectweek.na-mic.org/PW43_2025_Montreal/Projects/TransitionSlicerDefaultBuildFromQt5ToQt6/).

#### Icon Updates

- @SamHorvath is coordinating the ongoing **icon refresh** effort.

- See related [Project Week 43 notes](https://projectweek.na-mic.org/PW43_2025_Montreal/Projects/IconRefreshIn3DSlicer/).

#### VTK 9.5 Update

- Slicer is being updated to use [`slicer-v9.5.0-2025-06-19-e70c856bd`](https://github.com/Slicer/VTK/commits/slicer-v9.5.0-2025-06-19-e70c856bd). See [PR-8427](https://github.com/Slicer/Slicer/pull/8427) frmo @jamesobutler

- Evaluate backporting [MR-12224](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/12224/diffs#note_1674239) for improved behavior or fixes.

#### SlicerLibs & Trame Integration

- **Segment Editor Effects** :

- **Layout Manager** :

- **Wheels & Extension Discovery** :

#### Telemetry

- The **SlicerTelemetry** extension is now being integrated into the Slicer ecosystem.

- **Current backend** for data collection (testing phase):  
[https://ber-dom.sao.dom.my.id/](https://ber-dom.sao.dom.my.id/)

---

<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 2, 2025, 1:27pm UTC](https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561/3 "2025-07-02T13:27:48Z")

</div>

# Bagdes

- We also discussed which badges, created mainly with [shields.io](http://shields.io), would make Slicer extensions (or other open-source projects) have a README.md with more aesthetic and professional appearance.  
See [BoneReconstructionPlanner extension](https://github.com/SlicerIGT/SlicerBoneReconstructionPlanner#bonereconstructionplanner) as example and the related [Project Week page](https://projectweek.na-mic.org/PW43_2025_Montreal/Projects/DynamicCitationCounterBadgeForPapersWithCode/)

---

<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: [July 2, 2025, 1:37pm UTC](https://discourse.slicer.org/t/2025-07-01-weekly-meeting/43561/4 "2025-07-02T13:37:03Z")

</div>

Yes, and related to what @mau_igna_06 mentioned we discussed if the extension cmake should have a dedicated entry for html that would be rendered on the extension manager page or if we should put html directly in the extension description text. Html is required for displaying the badges. For now the badges can be in the README.md of the extension repository.
