# 2021.04.13 Hangout
**URL:** https://discourse.slicer.org/t/2021-04-13-hangout/17045
**Category:** Weekly meetings
**Created:** [April 12, 2021, 6:49pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045 "2021-04-12T18:49:18Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)
#### Post date: [April 12, 2021, 6:49pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/1 "2021-04-12T18:49:18Z")
Tomorrow, we will be having our next weekly hangout at 10:00 AM ET until 11 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:
- Slicer 5
- [PR-5349 - Pluggable markups](https://github.com/Slicer/Slicer/pull/5349)
Feel free to post to this thread to request/suggest a topic!
Thanks
Sam and J-Christophe
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [April 12, 2021, 10:06pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/2 "2021-04-12T22:06:23Z")
We should have a place to communicate the Slicer roadmap (what modules, features we plan to add/deprecate/remove). Need to find a good place for that.
- Wiki: Traditionally, we would put this on the wiki, but we are moving away from the wiki (not interactive enough, new users cannot register, it uses wiki markup instead of markdown, etc.).
- ReadTheDocs: It does not really belong to the Slicer source code repository. It is planning/management document, which does not need Slicer version-specific archival (and we don’t want to see very much outdated roadmaps in old Slicer documentation). We should link to the roadmap document from readthedocs, though.
- Discourse: We could add a new category or add just a new topic within Development. [“Wiki” style post can be created](https://meta.discourse.org/t/how-to-create-a-wiki-post/30802) that all users with wiki editing rights can modify.
- Google docs or Office online: This would work well while collaborating actively on a working document, but it is not well suited for long-term maintenance and discussion with a broad community.
None of the options are perfect but probably a wiki-style discourse topic would work the best, because users could easily subscribe to see changes and participate in the discussions around it.
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [April 12, 2021, 10:16pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/3 "2021-04-12T22:16:25Z")
Agreed, some clarity and buy-in on the plans would be helpful for everyone.
Another option could be to use github issues for the details and then a readme.md to track the high level. Could also use a github project to organize issues.
---
### Author:  [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [April 12, 2021, 10:24pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/4 "2021-04-12T22:24:54Z")
I would suggest a separate repo (so not source code) on github, because Markdown is so much easier for writing documents (if you are not anticipating a lot of figure or graphics etc).
Google docs is an option. If persistence and some sort of tracking is important perhaps you can consider [OSF.io](http://OSF.io), which offers google docs, and github integration. There are some examples here: [OSF | Curated List of OSF Example Projects Wiki](https://osf.io/rfe6k/wiki/home/)
Probably the most relevant is the working group/committee example…
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [April 12, 2021, 10:40pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/5 "2021-04-12T22:40:47Z")
> [@pieper](#):
>
> Another option could be to use github issues for the details and then a readme.md to track the high level. Could also use a github project to organize issues.
I would advocate for embracing GitHub for more project management functionality.
- GitHub issues for details of individual “Add New Thing” / “Deprecate Thing”.
- GitHub milestones to detail which things are in the near term or long term. With the new goal of quarterly stable releases, I think it would make sense to have “2021 Q1”/“2021 Q2”/“2021 Q3”/“2021 Q4” milestones that would more clearly detail what things are actively being worked on, versus will be worked on in a few months, in many many months, etc.
- [GitHub Wiki](https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis) functionality for details regarding roadmaps. When you go to create a wiki for a repo it states:
> Wikis provide a place in your repository to lay out the roadmap of your project, show the current status, and document software better, together.
You can see how a mature project like Visual Studio Code use the GitHub wiki to detail their roadmap. [https://github.com/microsoft/vscode/wiki/Roadmap](https://github.com/microsoft/vscode/wiki/Roadmap). The wiki is Markdown based. It can be updated by many people by modifying files which are contained in a separate repo. [https://github.com/Microsoft/vscode-wiki](https://github.com/Microsoft/vscode-wiki).
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [April 12, 2021, 11:18pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/6 "2021-04-12T23:18:02Z")
Yes, I like the way VS Code does it.
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [April 13, 2021, 5:08am UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/7 "2021-04-13T05:08:14Z")
@jamesobutler Using the github wiki is a great idea. We could gradually move over there all Slicer version independent content from the old wiki.
I like the vscode roadmap, too. That project is a few magnitudes larger than Slicer, but there are some useful concepts to adopt.
As a test, I’ve enabled the wiki and added some content - see here:
> **[Slicer/Slicer](https://github.com/Slicer/Slicer/wiki/Roadmap)**
>
> Roadmap
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [April 13, 2021, 3:44pm UTC](https://discourse.slicer.org/t/2021-04-13-hangout/17045/8 "2021-04-13T15:44:18Z")
Discussed:
- Improve Discourse category/tag to better track which post is related to extension build issue
- Roadmap organization
- Added roadmap to the wiki. See [Roadmap · Slicer/Slicer Wiki · GitHub](https://github.com/Slicer/Slicer/wiki/Roadmap)
- Edit is currently not restricted. We will re-assess if it is a sustainable approach.
Action items:
- Add note to hangout post (@jcfr ) ✅
- Check to increase monthly from 50 to 75 to have 10 admins (@jcfr ) ✅
- Message sent to discourse admins, message sent to Kitware team
- Create issue + PR related to config of extension using Python3 (@jcfr )
- [ENH: Pluggable Markups PR-5349](https://github.com/Slicer/Slicer/pull/5349) (@RafaelPalomar )
- Add Andras, Steve, Kyle as co author ✅
- merge ✅
- Create PR/issue related to build failure using dockbuild (@RafaelPalomar )
- Update readthedocs (and [slicer.org](http://slicer.org)) to reference roadmap (@lassoan)
- roadmap:
- Describe expectation regarding timeline and expectation
- Describe who can contribute
- Update regular wiki to “redirect” to new wiki roadmap (@lassoan)
- [Roadmap - Slicer Wiki](https://www.slicer.org/wiki/Roadmap)
- [Documentation/Labs - Slicer Wiki](https://www.slicer.org/wiki/Documentation/Labs#Roadmap)
- [Documentation/Labs/Slicer5-roadmap - Slicer Wiki](https://www.slicer.org/wiki/Documentation/Labs/Slicer5-roadmap)
- Improve guideline for creating post to suggest user to add tag (@lassoan)