(no commit message)

[wiki.git] / projects / collaboration.mdwn

diff --git a/projects/collaboration.mdwn b/projects/collaboration.mdwn
index 1f3ad8f2f2f7e541229c050a0dd90d769c58fea6..a70ad4fb29d70e887eb5cebfcc4031e0c7f3e2c7 100644 (file)
--- a/projects/collaboration.mdwn
+++ b/projects/collaboration.mdwn
@@ -53,6 +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.
+ * 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.