From: ls-ocaml-developer-2006@m-e-leypold.de
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml-developer mailing-list: subscribe now!
Date: Mon, 12 Mar 2007 10:25:22 +0100 [thread overview]
Message-ID: <4xbqiyoltp.fsf@hod.lan.m-e-leypold.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0703111900040.2875@droopy> (Martin Jambon's message of "Sun, 11 Mar 2007 19:21:48 -0700 (PDT)")
Martin Jambon <martin.jambon@ens-lyon.org> writes:
> On Mon, 12 Mar 2007, ls-ocaml-developer-2006@m-e-leypold.de wrote:
>
>> Martin Jambon <martin.jambon@ens-lyon.org> writes:
>>
>>> On Sun, 11 Mar 2007, ls-ocaml-developer-2006@m-e-leypold.de wrote:
>>>
>>>>> 2) Skipping all the unnecessary "language geekiness" stuff
>>>>
>>>> And that cannot be done by hand so that we have to split the community?
>>>
>>> Having to do things by hand is never really a good sign.
>>
>> Really? But how will the relevant mail be distributed to the
>> relevant lists? Aren't we deciding by hand to which list the mail goes
>> and isn't this prone to errors (i.e. "language geekiness" turning up
>> at your list and pedestrian mail turning up at caml-list)? And if the
>> splitting of mail by topics ("by hand") doesn't work well enough,
>> we'll all have to subscribe to two lists. How annoying.
>
> There are 1000 readers per message but only one author. To me it seems
> fair that the author of a message spends approximately 1000 times more
> effort than it takes to read and delete the message.
This is all nice and very moral, but: According to which criteria has
the writer to select the list? No language geekiness at your list,
that much is clear :-], but he/she can as well post almost anything to
caml-list according to the charter of caml-list. This doesn't bode
well for a distinctive sorting ...
>> And fragmentation hurts especially the newcomers who will often only
>> find and search one archive/list and then go away disapppointed (or
>> enraged).
>
> People search the whole web with their favorite search engine, don't they?
More Googleization at work. I dislike it. The internet is not only the
web. Which brings me to another point against Google groups: There is
no downloadable archive of messages (say in mbox format) which one can
download and index/search locally by the program of ones
choice. Basically all messages (as a whole) are locked into Google for
the rest of time and every time one wants to find anything, one also
furthers Googles business. At the long run a dear price to pay for a
"free service".
>> And: Will the CAML weekly news editor also read you list?
>
> I am not asking that from him, but yes he kindly proposed to do
> so. Thanks again Alan!
Good. IMHO that rather upgrades the status of the new list.
Regards -- Markus
next prev parent reply other threads:[~2007-03-12 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 20:02 Martin Jambon
2007-03-10 16:34 ` [Caml-list] " Daniel Bünzli
2007-03-10 20:32 ` Martin Jambon
2007-03-10 20:56 ` Joel Reymont
2007-03-11 3:10 ` Martin Jambon
2007-03-11 10:07 ` Gabriel Kerneis
2007-03-11 23:25 ` Richard Jones
2007-03-11 23:55 ` Oliver Bandel
2007-03-12 0:18 ` Erik de Castro Lopo
2007-03-29 0:34 ` Jon Harrop
2007-03-11 15:11 ` ls-ocaml-developer-2006
2007-03-12 1:28 ` Martin Jambon
2007-03-12 1:49 ` ls-ocaml-developer-2006
2007-03-12 2:21 ` Martin Jambon
2007-03-12 9:25 ` ls-ocaml-developer-2006 [this message]
2007-03-13 16:53 ` Nathaniel Gray
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=4xbqiyoltp.fsf@hod.lan.m-e-leypold.de \
--to=ls-ocaml-developer-2006@m-e-leypold.de \
--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