Difference between revisions of "Developer Meetings/20170418"
From Slicer Wiki
| Line 17: | Line 17: | ||
** Talked about notification associated with discourse. By default, users were not notified by new post. Isaiah updated the settings. | ** Talked about notification associated with discourse. By default, users were not notified by new post. Isaiah updated the settings. | ||
** "New (N)" indicates N topic were created since last visit | ** "New (N)" indicates N topic were created since last visit | ||
| − | ** Google Analytics of discourse vs wiki: Isaiah and Greg will talk. See also https://www.mediawiki.org/wiki/User:Dantman/Analytics_integration | + | ** Google Analytics of discourse vs wiki: |
| + | *** Isaiah and Greg will talk. See also https://www.mediawiki.org/wiki/User:Dantman/Analytics_integration | ||
| + | *** Our "GA code" will be added to the wiki | ||
** In the name of transparency, the Staff category will be made public but will be read-only | ** In the name of transparency, the Staff category will be made public but will be read-only | ||
** Next week we will assess with we notify user and developer to transition to discourse. | ** Next week we will assess with we notify user and developer to transition to discourse. | ||
Revision as of 14:40, 18 April 2017
Home < Developer Meetings < 20170418
 |
If you would like to list your topic here, create a wiki account and edit this page You can join the hangout using http://bit.ly/slicer-hangout-kw. |
To Discuss
- http://discourse.slicer.org/ - Where do we stand ? Did we address all concern ?
- PR#702 Use header metadata to initialize volume scalar range
Conclusion
- Discourse
- Talked about notification associated with discourse. By default, users were not notified by new post. Isaiah updated the settings.
- "New (N)" indicates N topic were created since last visit
- Google Analytics of discourse vs wiki:
- Isaiah and Greg will talk. See also https://www.mediawiki.org/wiki/User:Dantman/Analytics_integration
- Our "GA code" will be added to the wiki
- In the name of transparency, the Staff category will be made public but will be read-only
- Next week we will assess with we notify user and developer to transition to discourse.
