Difference between revisions of "Developer Meetings/20170418"

From Slicer Wiki
Jump to: navigation, search
Line 22: Line 22:
 
** 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.
 +
 +
* Landing page
 +
** Transitioning to Github hosting makes sense: http://slicer.github.io/slicer.org/ and https://github.com/Slicer/slicer.org/tree/gh-pages
 +
** At first, will be using cloud flare to serve as https. If it fails, we will have a failover plan for using paid hosting for https

Revision as of 14:55, 18 April 2017

Home < Developer Meetings < 20170418


Smile.png
 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

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:
    • 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.
Retrieved from "https://www.slicer.org/w/index.php?title=Developer_Meetings/20170418&oldid=51082"