# Free software
-For software and source code, the [[SIPB project licensing recommendation|doc/licensing]] advises you to choose one of the following two licenses:
+For software and source code, the [[SIPB project licensing recommendation|doc/code-licensing]] advises you to choose one of the following two licenses:
* the <a>MIT license</a>, also known as the "Expat" or "X11" license. This is a short, permissive license that allows code to be distributed and reused in most forms, without placing redistribution requirements on the user or distributor.
# Free documentation
-The [[doc/doc-licensing|SIPB documentation licensing recommendation]] advises *dual-licensing* (i.e., making available with both licenses) documentation under:
+The [[SIPB documentation licensing recommendation|doc/doc-licensing]] advise *dual-licensing* (i.e., making available with both licenses) documentation under:
+
* the <a>Creative Commons Attribution-Share Alike</a> license, and
* the <a>GNU Free Documentation License</a>, with no Invariant Sections, no Front-Cover Texts, and no Back-Cover-Texts.
A license without the code is worthless! Make sure your code is posted somewhere accessible. If you're using a version control system (which you should), the easiest approach is to set up public read-only access to your repository. Options that SIPB projects have used include
- * <a>Subversion on Athena</a>
+ * <a>Subversion or git in an Athena AFS locker</a>
* <a>Subversion or git on scripts.mit.edu</a>
* <a>Github</a>, a commercial git hosting service free for open-source/public projects