# 2019.11.26 Hangout

**URL:** <https://discourse.slicer.org/t/2019-11-26-hangout/9303>\
**Category:** Weekly meetings\
**Created:** [November 26, 2019, 1:44pm UTC](https://discourse.slicer.org/t/2019-11-26-hangout/9303 "2019-11-26T13:44:11Z")\
**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:** [November 26, 2019, 1:44pm UTC](https://discourse.slicer.org/t/2019-11-26-hangout/9303/1 "2019-11-26T13:44:11Z")

</div>

Hi,

Today, we will be having our weekly hangout at 10:00 AM EST until 10:30 AM.

Agenda:

- Slicer 5.0 release schedule

The [project week call](https://discourse.slicer.org/t/project-week-33-january-20-24-2020-in-las-palmas-gran-canaria/8734) will begin at 10:30

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)

Feel free to post to this thread to request/suggest a topic!

Thanks  
Sam

---

<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:** [November 26, 2019, 10:23pm UTC](https://discourse.slicer.org/t/2019-11-26-hangout/9303/2 "2019-11-26T22:23:26Z")

</div>

> Slicer 5.0 release schedule

The plan is to release Slicer 5.0 shortly after the [33rd Project Week](https://projectweek.na-mic.org/PW33_2020_GranCanaria/)

We updated the [Slicer roadmap](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap) adding a new section called `Slicer 5.2: Backward incompatible changes` and retargeted some of the low priority tasks.

During the project week, we plan on:

- discussing how to improve the MRML Copy API and hopefully make good progress
- implementing the following changes:
  - Update default [Coordinate system in STL files](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Coordinate_system_in_files)
  - Update default for [Acquisition transform](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Acquisition_transform)
  - Updating the [Extension description file format](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Extension_description_file_format)

### Pending questions

- @cpinter Do you know what is the status regarding [Model Hierarchies](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Model_Hierarchies) ?

- As planned, should we remove the legacy [Editor](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Editor) ? My vote is **yes**.

## Next hangout

We will review remaining items on the roadmap (CLI to be removed, …)

---

<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:** [November 26, 2019, 10:41pm UTC](https://discourse.slicer.org/t/2019-11-26-hangout/9303/3 "2019-11-26T22:41:34Z")

</div>

Thanks for the summary Jc, I look forward to the follow on discussions and work 👍

> [@jcfr](#):
>
> As planned, should we remove the legacy [Editor](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap#Editor) ? My vote is **yes**.

On this note I think the question is whether there are still any extensions that rely on this legacy code. Personally I don’t mind seeing the Editor module disappear, but at the same time I don’t think it hurts anything to have it included in a legacy and deprecated condition.

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [November 29, 2019, 4:46pm UTC](https://discourse.slicer.org/t/2019-11-26-hangout/9303/4 "2019-11-29T16:46:34Z")

</div>

As far as I know, model hierarchies now work well with subject hierarchy. There were I think two bugs, but those have been already resolved.