Note that module packages must be git repositories

Author: mxcl

Documentation/SystemModules.md

@@ -49,6 +49,13 @@ contains more “Swifty” function wrappers around the raw C interface.
 > When you are done you should push to GitHub or another hosting site so
 > the wider community can benefit from your work.
 
+Packages must be semantically-versioned git repositories, so in the `CVorbis` directory:
+
+    git init
+    git add .
+    git commit -m "Initial Commit"
+    git tag 1.0.0
+
 We must do the same for `libogg`:
 
     module COgg [system] {
@@ -57,10 +64,16 @@ We must do the same for `libogg`:
         export *
     }
 
+And then again in the `COgg` directory:
+
+    git init
+    git add .
+    git commit -m "Initial Commit"
+    git tag 1.0.0
 
 Note we do not call the module `CLibogg`. In general, avoid the lib prefix unless the authors of the package
 typically always refer to it that way. A good rule of thumb is to look at the header files, here we can
-see the header is called simply "ogg.h". Pay attention to capitalization; note that we provide `CPOSIX` and not
+see the header is called simply "ogg.h". Pay attention to capitalization; it would be `CPOSIX` and not
 `CPosix`, because POSIX is an acronym and is typically spelled all-caps.
 
 Back in our example app we need a `Package.swift` that depends on CVorbis: