# 2025.07.08 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2025-07-08-weekly-meeting/43572>\
**Category:** Weekly meetings\
**Created:** [July 2, 2025, 1:19am UTC](https://discourse.slicer.org/t/2025-07-08-weekly-meeting/43572 "2025-07-02T01:19:43Z")\
**Posts on this page:** 4\
**Page:** 1

<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-08-weekly-meeting/43572/1 "2025-07-02T01:19:44Z")

</div>

Next week, 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 8, 2025, 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:** ![hjmjohnson](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hjmjohnson/32/173_2.png) [@hjmjohnson](https://discourse.slicer.org/u/hjmjohnson)\
**Post date:** [July 2, 2025, 7:01pm UTC](https://discourse.slicer.org/t/2025-07-08-weekly-meeting/43572/2 "2025-07-02T19:01:58Z")

</div>

**Agenda:**

- Discuss code formatting conventions and plan to implement an automated code formatter.  
[PR 8525](https://github.com/Slicer/Slicer/pull/8525)  
[PR 7603](https://github.com/Slicer/Slicer/pull/7603)  
[Issue 5211](https://github.com/Slicer/Slicer/issues/5211)  
[Weekly Meeting Agenda](https://discourse.slicer.org/t/2024-02-27-weekly-meeting/34553)

- Strategize Qt6 upgrades

---

<div class="post-metadata">

**Author:** ![hjmjohnson](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hjmjohnson/32/173_2.png) [@hjmjohnson](https://discourse.slicer.org/u/hjmjohnson)\
**Post date:** [July 8, 2025, 12:20pm UTC](https://discourse.slicer.org/t/2025-07-08-weekly-meeting/43572/3 "2025-07-08T12:20:32Z")

</div>

CTK: Upgrades:

- [update ci build submissions to add clazy support by hjmjohnson · Pull Request #1241 · commontk/CTK · GitHub](https://github.com/commontk/CTK/pull/1241). → [CTK](https://my.cdash.org/index.php?project=CTK)
- [COMP: Update PythonQt to branch based off upstream v3.6.1 by jamesobutler · Pull Request #1240 · commontk/CTK · GitHub](https://github.com/commontk/CTK/pull/1240). → PythonQt updates
- [COMP: Add AUTO(MOC|UIC|RCC) build. Add missing Q\_OBJECT for decendants of QObject by hjmjohnson · Pull Request #1239 · commontk/CTK · GitHub](https://github.com/commontk/CTK/pull/1239) (AUTO(MOC|UIC|RCC) + Q\_OBJECT additions
- DRAFT NEXT EFFORTS (Qt Compliance for best practices, 5000+ clazy warnings)  
- [COMP: Fix NOTIFY warnings in Q\_PROPERTIES by hjmjohnson · Pull Request #1242 · commontk/CTK · GitHub](https://github.com/commontk/CTK/pull/1242/commits/9d9acc18ab1919be21273410be2984e5a52ae5ae)  
- [COMP: Fix NOTIFY warnings in Q\_PROPERTIES by hjmjohnson · Pull Request #1242 · commontk/CTK · GitHub](https://github.com/commontk/CTK/pull/1242/commits/a997735f27e3fcfc75a739a39f5c6d341df1bf99)

---

<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 15, 2025, 3:29pm UTC](https://discourse.slicer.org/t/2025-07-08-weekly-meeting/43572/4 "2025-07-15T15:29:56Z")

</div>

## Meeting Notes

### Welcome New Attendees

We were pleased to welcome the following new participants:

- Kate Wooley
- Kat Dunn
- Andy Huynh

### Use of `clang-format` for C++ Code

- Discussed the use of `clang-format` for automatic C++ code formatting.
- General consensus on the **importance of consistent formatting** across the codebase.
- Two main strategies considered:
  - **Incremental adoption** (formatting new/modified code).
  - **Full project-wide formatting** in a single commit.

- Opinions were divided on the best approach.
- Related work:
  - Proposed: [PR #8525](https://github.com/Slicer/Slicer/pull/8525)
  - Previous: [PR #7603](https://github.com/Slicer/Slicer/pull/7603)

- An **alternative approach** suggested: enable but not enforce formatting in the beginning.
- Plan to **finalize the decision by next week**.

### CTK Updates

- Reviewed recent updates in **CTK** :
  - [PR #1239](https://github.com/commontk/CTK/pull/1239): General updates and fixes.
  - [PR #1240](https://github.com/commontk/CTK/pull/1240): Update **PythonQt** to upstream version 3.6.1.
  - [PR #1241](https://github.com/commontk/CTK/pull/1241): Use of **Clazy** in GitHub workflows to surface Qt6 migration warnings.

### Support for Distributing Commercial Extensions

- Reviewed ideas for improving **commercial extension support** :

### Refactoring `Slicer.util`

- The `slicer.util` module currently contains a mix of legacy and new functionality.

- Many deprecated or unstructured utilities are still present.

- Instead of continuing on the deprecation path, the group recommended:

### Telemetry

- Discussed ongoing telemetry work and feedback.
- See: [SlicerTelemetry Issue #2](https://github.com/Slicer/SlicerTelemetry/issues/2#issuecomment-3049154918)