From: "Benjamin C. Pierce" <bcpierce@saul.cis.upenn.edu>
To: Pierre Weis <Pierre.Weis@inria.fr>
Cc: garrigue@kurims.kyoto-u.ac.jp (Jacques Garrigue), caml-list@inria.fr
Subject: Re: Newsgroup for Caml?
Date: Thu, 15 Jun 2000 08:53:39 EDT [thread overview]
Message-ID: <2844.961073619@saul.cis.upenn.edu> (raw)
In-Reply-To: Your message of Thu, 15 Jun 2000 13:29:14 +0200. <200006151129.NAA05959@pauillac.inria.fr>
> > What about keeping a moderated caml-list mainly for announcements, the
> > newsgroup being there for questions and discussions?
>
> Yes, but I would like a slightly more general mailing list, opened to
> suggestions (libraries and language design improvements). The rest
> (including comparison between Caml and whatever) being freeely posted
> to the unmoderated newsgroup.
I agree that the volume of traffic on the caml-list is close to
becoming a problem, but I'm not completely happy with the idea of an
unmoderated newsgroup: in my experience, they *always* fill up with
spam, off-topic discussions, and other kinds of garbage. I would
personally not read such a newsgroup.
One of the best things about the caml language at the moment is that
it has such a strong community of developers and power-users.
Maintaining a *high-quality* (= carefully moderated) channel of
communication is one of the most important ways of keeping this
community together.
If answering newbie questions is getting to be too much work, why not
redirect them to comp.lang.ml? -- after all, there are plenty of
newbie SML questions there.
-- B
P.S. I do know that dealing with mailing list moderation takes time:
the Types list (www.cis.upenn.edu/~bcpierce/types) often gets 10 or 20
postings in a day, of which I usually end up rejecting or responding
myself to more than 2/3. But having a high-signal-to-noise forum for
that community (like this one) seems valuable and I don't see any
other way to achieve it than somebody doing significant work on
filtering messages.
P.P.S. Moving some or all of the caml-list discussions to a
*moderated* newsgroup might be worth considering (I agree that these
are easier to manage for readers), but I believe even moderated usenet
groups are pretty easy to spam.
next prev parent reply other threads:[~2000-06-15 16:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 19:05 Daniel de Rauglaudre
2000-06-13 16:53 ` Pierre Weis
2000-06-13 23:18 ` Markus Mottl
2000-06-15 3:07 ` Jacques Garrigue
2000-06-15 11:29 ` Pierre Weis
2000-06-15 12:53 ` Benjamin C. Pierce [this message]
2000-06-15 20:36 ` Michael Vanier
2000-06-15 12:22 ` Markus Mottl
2000-06-16 8:01 ` Sven LUTHER
2000-06-14 8:08 ` Jean-Yves Moyen
2000-06-13 19:16 ` Michael Vanier
2000-06-15 13:47 ` Xavier Leroy
2000-06-16 8:07 ` Niall Dalton
2000-06-16 16:44 ` Daniel de Rauglaudre
2000-06-16 8:32 ` Jacques Garrigue
2000-06-16 11:25 ` Alexander I. Zhezherun
2000-06-13 17:02 Dave Berry
2000-06-14 7:18 ` Sven LUTHER
2000-06-15 9:22 Dave Berry
2000-06-15 12:31 Damien Doligez
2000-06-15 13:32 Dave Berry
2000-06-16 18:41 Brent Fulgham
2000-06-19 10:24 ` Jean-Francois Monin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2844.961073619@saul.cis.upenn.edu \
--to=bcpierce@saul.cis.upenn.edu \
--cc=Pierre.Weis@inria.fr \
--cc=bcpierce@cis.upenn.edu \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox