X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/cc06c9bd8c81638a9caae765b9fd7c85cb483c4b..04ffeb2bb0b6b6bf48060f2f20c508d2b01aa16f:/projects/collaboration.mdwn

diff --git a/projects/collaboration.mdwn b/projects/collaboration.mdwn
index 72b683a..8cdd896 100644
--- a/projects/collaboration.mdwn
+++ b/projects/collaboration.mdwn
@@ -29,9 +29,9 @@ There are other licenses, most notably including the <a>BSD license</a>, which i
 
 For a permissive license, MIT and BSD are basically equivalent ([MIT TLO](http://tlo.mit.edu/community/software) recommends BSD online, but in person indicates that they don't differentiate). We recommend MIT over BSD just because much of Athena already uses it, [MIT appears substantially more popular](https://github.com/blog/1964-license-usage-on-github-com), and [Github recommends it](https://choosealicense.com/).
 
-We anticipate that most SIPB projects' needs are best served by selecting either the MIT license or the GPL and moving on. However, if you are interested in this subject, you can learn more at [GNU's licensing website](http://www.gnu.org/licenses/) and [the Open Source Initiative's](http://www.opensource.org/licenses/). You can also read more about free and open source
+We anticipate that most SIPB projects' needs are best served by selecting either the MIT license or the GPL and moving on. However, if you are interested in this subject, you can learn more at [GNU's licensing website](https://www.gnu.org/licenses/) and [the Open Source Initiative's](https://www.opensource.org/licenses/). You can also read more about free and open source
 software on GNU and OSI's websites; see also the [Debian Free
-Software Guidelines](http://www.debian.org/social_contract#guidelines) and an [FAQ for it](http://people.debian.org/~bap/dfsg-faq.html).
+Software Guidelines](https://www.debian.org/social_contract#guidelines) and an [FAQ for it](https://people.debian.org/~bap/dfsg-faq.html).
 
 # Free documentation
 
@@ -53,7 +53,7 @@ A license without the code is worthless! Make sure your code is posted somewhere
 Code without an idea of development progress isn't worthless, but it's still not quite optimal. Again, options that SIPB projects use include
 
  * A development <a>mailing list</a> that's public or open to interested contributors on request.
- * Publicly readable <a>archives</a> of your mailing list. (Mailman lists support archiving, or you can add a Discuss archive, for example using [Pergamon](https://sipb.mit.edu/doc/pergamon/).)
+ * Publicly readable <a>archives</a> of your mailing list. (Mailman lists support archiving, or you can add a Discuss archive, for example using [[Pergamon|/doc/pergamon]].)
  * <a>Trac</a>, a bug tracker and source code browser available via the scripts.mit.edu autoinstaller.
  * <a>Github</a> issues.
  * <a>Launchpad</a>, the bug tracker and source code / Debian package host that Ubuntu developed and opened to others.