* 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.
* 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 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 or git on scripts.mit.edu</a>
* <a>Github</a>, a commercial git hosting service free for open-source/public projects
* <a>Subversion or git on scripts.mit.edu</a>
* <a>Github</a>, a commercial git hosting service free for open-source/public projects