caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Benjamin C. Pierce" <bcpierce@saul.cis.upenn.edu>
To: brogoff@speakeasy.net
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Moderation
Date: Tue, 22 Oct 2002 10:21:43 EDT	[thread overview]
Message-ID: <27992.1035296503@saul.cis.upenn.edu> (raw)
In-Reply-To: Your message of Mon, 21 Oct 2002 10:21:12 -0700. <Pine.LNX.4.44.0210210944350.25233-100000@grace.speakeasy.net>

The main issue I see with the caml-list is not lack of moderation: like
everyone, I'd prefer to have the spam and trolls filtered a bit better,
but there's really not that much of that stuff.  The more serious problem
is the ever-increasing volume of *interesting* messages!

OCaml is a central tool in my work (right up there with Emacs and TeX
:-), and I feel it's quite important for me to stay on top of what's
happening in the community, participate in discussions of new features,
learn about dark corners and subtle gochas, find out about plans for the
future, etc.  But lately it's been getting to be a significant burden
even to scan message headers -- on some days, caml-list accounts for a
third of all the (non-spam) mail I receive.

Since the problem is essentially too much of a good thing, it's hard to
see what could be a complete solution.  But I think there are several
little steps that can help.  Having a separate caml-announce list is a
good step, and I hope people get (even more) in the habit of using it to
let others know about useful stuff.  I also wonder whether someone
(perhaps Alan Schmitt, who does something similar already?) could try
posting occasional "minutes" of the discussions on the list, so that
people like me could check in and see what's been going on without trying
to read every message.

Regards,

        Benjamin

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-10-22 14:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 15:54 brogoff
2002-10-18 16:03 ` Georges Brun-Cottan
2002-10-18 16:42   ` Nicolas Cannasse
2002-10-18 19:03     ` Sven Luther
2002-10-18 19:33       ` Nicolas Cannasse
2002-10-19  6:28         ` Sven Luther
2002-10-18 16:50   ` Mattias Waldau
2002-10-19  0:58     ` Alan Schmitt
2002-10-21  7:01     ` Maxence Guesdon
2002-10-22 14:46   ` [Caml-list] GlSurf: surface in OCaml/OpenGL Christophe Raffalli
2002-10-19  0:11 ` [Caml-list] Moderation Stefano Zacchiroli
2002-10-21 13:47 ` Xavier Leroy
2002-10-21 14:09   ` Alessandro Baretta
2002-10-21 17:21   ` brogoff
2002-10-22 14:21     ` Benjamin C. Pierce [this message]
2002-10-22 14:56       ` Alan Schmitt
2002-10-22 20:48         ` Michael Vanier
2002-10-22 21:55           ` Alan Schmitt
2002-10-25  7:35             ` Didier Remy
2002-10-28 15:40               ` Alan Schmitt
2002-10-28 19:33                 ` Alan Schmitt
2002-10-18 19:40 Ishmael Yavitz

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=27992.1035296503@saul.cis.upenn.edu \
    --to=bcpierce@saul.cis.upenn.edu \
    --cc=bcpierce@cis.upenn.edu \
    --cc=brogoff@speakeasy.net \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).