From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: Newsgroup for Caml?
Date: Thu, 15 Jun 2000 14:22:38 +0200 [thread overview]
Message-ID: <20000615142238.A31680@miss.wu-wien.ac.at> (raw)
In-Reply-To: <20000615120749F.garrigue@kurims.kyoto-u.ac.jp>; from garrigue@kurims.kyoto-u.ac.jp on Thu, Jun 15, 2000 at 12:07:49 +0900
On Thu, 15 Jun 2000, Jacques Garrigue wrote:
> > Instead of creating a new one, the more imperialistically minded among us
> > might choose to seize power over there...
>
> Well, the problem is that comp.lang.ml is a moderated newsgroup, and
> that it is directly tied to the SML mailing list. I see no point in
> changing that.
I was only joking ;-)
But in any case: traffic is really low there. I could imagine that
it would be beneficial for the ML-communities not to split up too
much. People look for newsgroups with high traffic, because this improves
the chance of discussing a topic of their interest.
Additionally, people would see that there are several ML-flavours around,
in other terms: the general style of ML is obviously a reasonable one
to adopt/learn.
A beginner will probably find out more easily about advantages and
drawbacks of the specific flavours and implementations if he has a
newsgroup where both sides can argue.
Although a separate newsgroup for Caml would still have a chance of
thriving, some "cultural" intermixture might lead to fruitful (and
hopefully flameless ;) discussions.
Pierre's proposal to still have a list for implementation specific
suggestions seems reasonable. One could cross-post messages from the
maintainers to the newsgroup.
> Also I'm not sure that people who don't like newsgroups would really
> enjoy reading such a non-moderated caml-list, with the flame-wars and
> spam one can expect.
Mailing lists, too, can contain flame wars - but here you cannot "escape"
so easily, because it clutters your mailbox.
> I know it's always hard to distinguish, but for me news and mailing
> lists are complementary, and I would prefer to have mailing lists
> directly pour in my inbox, rather than have to discriminate them to
> avoid overflow.
I personally can live with both alternatives. The question is whether
Pierre wants to become a full-time list moderator or prefers to do
some research...
Best regards,
Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~2000-06-15 16:09 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
2000-06-15 20:36 ` Michael Vanier
2000-06-15 12:22 ` Markus Mottl [this message]
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=20000615142238.A31680@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--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