Commit | Line | Data |
---|---|---|
7f918cf1 CE |
1 | Contact |
2 | ======= | |
3 | ||
4 | == Mailing lists == | |
5 | ||
6 | There are three mailing lists available. | |
7 | ||
8 | * mailto:MLton-user@mlton.org[`MLton-user@mlton.org`] | |
9 | + | |
10 | MLton user community discussion | |
11 | + | |
12 | -- | |
13 | * https://lists.sourceforge.net/lists/listinfo/mlton-user[subscribe] | |
14 | https://sourceforge.net/mailarchive/forum.php?forum_name=mlton-user[archive (SourceForge; current)], | |
15 | http://www.mlton.org/pipermail/mlton-user/[archive (PiperMail; through 201110)] | |
16 | -- | |
17 | ||
18 | * mailto:MLton-devel@mlton.org[`MLton-devel@mlton.org`] | |
19 | + | |
20 | MLton developer community discussion | |
21 | + | |
22 | -- | |
23 | * https://lists.sourceforge.net/lists/listinfo/mlton-devel[subscribe] | |
24 | https://sourceforge.net/mailarchive/forum.php?forum_name=mlton-devel[archive (SourceForge; current)], | |
25 | http://www.mlton.org/pipermail/mlton-devel/[archive (PiperMail; through 201110)] | |
26 | -- | |
27 | ||
28 | * mailto:MLton-commit@mlton.org[`MLton-commit@mlton.org`] | |
29 | + | |
30 | MLton code commits | |
31 | + | |
32 | -- | |
33 | * https://lists.sourceforge.net/lists/listinfo/mlton-commit[subscribe] | |
34 | * https://sourceforge.net/mailarchive/forum.php?forum_name=mlton-commit[archive (SourceForge; current)], | |
35 | http://www.mlton.org/pipermail/mlton-commit/[archive (PiperMail; through 201110)] | |
36 | -- | |
37 | ||
38 | ||
39 | === Mailing list policies === | |
40 | ||
41 | * Both mailing lists are unmoderated. However, the mailing lists are | |
42 | configured to discard all spam, to hold all non-subscriber posts | |
43 | for moderation, to accept all subscriber posts, and to admin approve | |
44 | subscription requests. Please contact | |
45 | mailto:matthew.fluet@gmail.com[Matthew Fluet] if it appears that your | |
46 | messages are being discarded as spam. | |
47 | ||
48 | * Large messages (over 256K) should not be sent. Rather, please send | |
49 | an email containing the discussion text and a link to any large files. | |
50 | ||
51 | ///// | |
52 | * Very active mailto:MLton-devel@mlton.org[`MLton@mlton.org`] list | |
53 | members who might otherwise be expected to provide a fast response | |
54 | should send a message when they will be offline for more than a few | |
55 | days. The convention is to put | |
56 | "++__userid__ offline until __date__++" in the subject line to make it | |
57 | easy to scan. | |
58 | ///// | |
59 | ||
60 | * Discussions started on the mailing lists should stay on the mailing | |
61 | lists. Private replies may be bounced to the mailing list for the | |
62 | benefit of those following the discussion. | |
63 | ||
64 | * Discussions started on | |
65 | mailto:MLton-user@mlton.org[`MLton-user@mlton.org`] may be migrated to | |
66 | mailto:MLton-devel@mlton.org[`MLton-devel@mlton.org`], particularly | |
67 | when the discussion shifts from how to use MLton to how to modify | |
68 | MLton (e.g., to fix a bug identified by the initial discussion). | |
69 | ||
70 | == IRC == | |
71 | ||
72 | * Some MLton developers and users are in channel `#sml` on http://freenode.net. |