Most tutorials are created using PowerPoint but published on the Slicer wiki as pdf. To facilitate contributions, we should make the source files available in GitHub. Which repository should we use?
There are these existing repositories that we might consider but we could also create a new one:
Do we want to manage the original slide document (ppt, …) as (1) “text file” or as (2) “release asset” ?
(1) this approach is well suited for document that compress well and can be efficiently managed using source control management like git. This does not apply for slide document because they do not compress well. (to some extent svn would be more suited as it would only check out one version of the document at a time)
(2) this approach is to both work around the fact a git repo would get large very quickly and leverage the free storage offered by GitHub.
The aim of this project was to host the actual html sources of a future portal for tutorial, I think original slide document (powerpoint, openoffice, …) should be uploaded somewhere else. May be as release assets ?
This repo hold the sources of the DataStore extension. I don’t think it is a good option.
This repo supports the upload of testing data as release assets and their retrieval based on their hashsum. Original slide documents could be uploaded there or in a different repo using a similar mechanism.
The original materials could be uploaded as release assets in a new SlicerTutorialData repository on GitHub.