# 2023.08.01 Weekly Meeting

**URL:** https://discourse.slicer.org/t/2023-08-01-weekly-meeting/30890
**Category:** Weekly meetings
**Created:** [July 31, 2023, 4:12pm UTC](https://discourse.slicer.org/t/2023-08-01-weekly-meeting/30890 "2023-07-31T16:12:30Z")
**Posts on this page:** 3
**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 31, 2023, 4:12pm UTC](https://discourse.slicer.org/t/2023-08-01-weekly-meeting/30890/1 "2023-07-31T16:12:30Z")

</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 to ask questions at [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)

* * *

**Agenda:**

- [Extension dashboard status](https://slicer.cdash.org/index.php?project=SlicerPreview#!#Extensions-Nightly)

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: ![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 31, 2023, 4:41pm UTC](https://discourse.slicer.org/t/2023-08-01-weekly-meeting/30890/2 "2023-07-31T16:41:24Z")

</div>

It would be nice if we could talk about this:

> [@Should we start collecting software usage data?](https://discourse.slicer.org/t/should-we-start-collecting-software-usage-data/30873/7):
>
> Any kind of non-networking task (e.g., starting a segmentation task) initiating network communication without explicit user approval could be interpreted by some users as spying. Users that are sensitive about tracking their activities install firewalls that immediately notify them about all network requests and they are upset if they find out that a software attempted to send information without consent, may start a smear campaign, etc. that we should all absolutely avoid. I think allowing send…

---

<div class="post-metadata">

### Author: ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [July 31, 2023, 4:51pm UTC](https://discourse.slicer.org/t/2023-08-01-weekly-meeting/30890/3 "2023-07-31T16:51:23Z")

</div>

It would be also nice to discuss about continuous integration for extensions:

> [@Adding a CI build to a Slicer extension](https://discourse.slicer.org/t/adding-a-ci-build-to-a-slicer-extension/30857/24):
>
> The standard for CI today is immediate build for pull requests. It would be nice to achieve this for Slicer, too. Currently, most extension developers rely on local builds and the nightly automatic build. The only exception is OpenDose3D, which has [CI pipeline](https://gitlab.com/opendose/opendose3d/-/pipelines) set up on gitlab.
