Publishing #164
Description
Opposite of installing a course, basically.
As the creator of a course I want to be able to take my completed course, studentify it and then publish that to a repository (or other public location from which students can install the course).
Creating a new repository?
git push?
Another alternative is to have the studentified courses be distributed as 'release' artifacts. Having a 'release' of a main repo result in the zip'd studentified directory being added to the releases of a the main repo would allow for releases courses to be versioned (semantically?)
The drawback would be more complication on the install side - where we couldn't use git clone for pulling and updating courses anymore, we'd have to download and unzip.
At that point we'd have the option of storing multiple versions of the same course. This would complicate things slight (would require maintaining a mapping of the current version of a course being used, as well as the course name as a key. I'm not sure of the benefits of maintaining multiple versions of a course locally, though. For the course creator to do some comparisons yes, but there should be more students for a course than creators and adding the necessary complexity (rather than just overwriting a course) as well as taking up space on their machines for the sake of this functionality doesn't seem worth it.