# 2023.01.10 Weekly Meeting

**URL:** https://discourse.slicer.org/t/2023-01-10-weekly-meeting/27142
**Category:** Weekly meetings
**Created:** [January 9, 2023, 10:27pm UTC](https://discourse.slicer.org/t/2023-01-10-weekly-meeting/27142 "2023-01-09T22:27:02Z")
**Posts on this page:** 2
**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: [January 9, 2023, 10:27pm UTC](https://discourse.slicer.org/t/2023-01-10-weekly-meeting/27142/1 "2023-01-09T22:27:02Z")

</div>

Tomorrow, we will be having our next weekly hangout at **11:00 AM ET until 12:00PM ET**. The time slot has been shifted due to the [Project Week preparation calls](https://discourse.slicer.org/t/na-mic-project-week-reminder-next-project-week-prep-meeting-tomorrow-tuesday-jan-10th/27141).

We will likely be re-using the [Project Week zoom call link](https://etsmtl.zoom.us/j/86211702920?pwd=TEl0ZTFDam90WVN5bjZhR05kNVRVZz09) as we have done previously.

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: ![RafaelPalomar](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rafaelpalomar/32/1436_2.png) [@RafaelPalomar](https://discourse.slicer.org/u/RafaelPalomar)
#### Post date: [January 10, 2023, 7:00pm UTC](https://discourse.slicer.org/t/2023-01-10-weekly-meeting/27142/2 "2023-01-10T19:00:10Z")

</div>

In the meeting today we (@pieper, @lassoan, @mau_igna_06, @Sam_Horvath, @Connor-Bowley, @RafaelPalomar) were discussing about some of the extensions tests failing due to missing dependencies during testing ([https://github.com/Slicer/Slicer/issues/6529](https://github.com/Slicer/Slicer/issues/6529))

One interesting idea that came up in the discussion was to do individual extension testing in separate containers where the dependencies are pulled-in (and possibly installed in the testing container); apparently dependencies in some extensions might alter the Slicer environment making other extensions not compatible. Along with this idea, there was a discussion on whether we could create/support infrastructure to allow developers to do the testing on their own with github actions or similar. This would effectively make the testing distributed, reduding the testing burden for the Slicer project.

@jcfr, as we have discussed the extensions testing before, it would be nice to know your thoughts on these ideas.