@@ -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.
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.
* <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.