caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Duane Johnson <duane.johnson@gmail.com>
To: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Cc: SP <sp@orbitalfox.com>,
	Gabriel Scherer <gabriel.scherer@gmail.com>,
	 Dean Thompson <deansherthompson@gmail.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] how to encourage adoption of OCaml?
Date: Fri, 8 Jul 2016 16:39:42 -0600	[thread overview]
Message-ID: <CAFLokDdctXZD_URH_mKDA98h4+Sbdb0OneA8A464OHtwBSg2EA@mail.gmail.com> (raw)
In-Reply-To: <CAHvkLrOO5n046xWoRunWaa+AUSqJs_U3F=5Xhr2PcL2-b15-6Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

On Fri, Jul 8, 2016 at 4:18 PM, Fabrice Le Fessant <
Fabrice.Le_fessant@inria.fr> wrote:

> Anyway, I am not fond of the multiplication of communication channels,
> they tend to divide an already small community into smaller groups, and it
> becomes hard to remain up-to-date with latest information. For example, a
> lot of discussions are now happening on Github pull-requests, either in
> ocaml/ocaml or ocaml/opam-repository, and if you don't keep an eye on them,
> you might soon discover that important decisions have been taken without
> most of the community knowing it.


When Twitter first came out, I wondered how I was supposed to read
everything in my stream because I couldn't always tell where I'd left off
last time. Then I learned some people followed *hundreds* of other twitter
users (at that time I had only started following a handful) and I realized
something different was going on--this wasn't a medium where I could drink
in every tweet, it was a firehose and I could come get splashed here and
there when I wanted to :)

I think there's a place for less consequential announcements and
discussions in a community--especially a large one. Important information
will almost always reach critical mass and the network will distribute it
to every leaf node. A mailing list is a good solid place for discussion,
and every incoming message can be addressed up to a certain threshold--but
when it gets too popular, even the long-time participants start to complain
that there's too much noise.

When the Haskell mailing list experienced this kind of growth, there was
someone in the community who took it upon themselves to summarize the
important announcements, events, and projects that had taken place in the
past week. People could be assured that even if they weren't personally
reading each of 100 messages per day, there was still a way to be apprised
of the headline events.

Perhaps someone could do the same, as a bridge between the github and
caml-list groups.

[-- Attachment #2: Type: text/html, Size: 2450 bytes --]

  reply	other threads:[~2016-07-08 22:39 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 10:01 Dean Thompson
2016-06-30 10:16 ` Kakadu
2016-06-30 10:41   ` Dean Thompson
2016-06-30 10:46   ` Anil Madhavapeddy
2016-06-30 10:17 ` Jeremy Yallop
2016-06-30 10:31   ` Dean Thompson
2016-06-30 12:12     ` Yaron Minsky
2016-06-30 13:13       ` Ivan Gotovchits
2016-07-01  0:13         ` Yaron Minsky
2016-07-01  0:41           ` [Caml-list] Async and lwt Hendrik Boom
2016-07-01  1:26             ` Yaron Minsky
2016-07-01 12:44           ` [Caml-list] how to encourage adoption of OCaml? Dean Thompson
2016-07-01 12:46             ` Yaron Minsky
2016-07-04 14:12           ` sp
2016-06-30 11:49 ` Gerd Stolpmann
2016-07-04 14:45 ` sp
2016-07-08 12:57   ` Dean Thompson
2016-07-08 13:45     ` Francois Berenger
2016-07-08 14:40     ` Gabriel Scherer
2016-07-08 15:16       ` Duane Johnson
2016-07-08 15:33         ` Roberto Di Cosmo
2016-07-08 16:25           ` Yotam Barnoy
2016-07-08 16:50             ` Roberto Di Cosmo
2016-07-08 16:54         ` Mohamed Iguernlala
2016-07-08 17:02           ` Yotam Barnoy
2016-07-08 17:09             ` Yotam Barnoy
2016-07-08 17:29               ` Kakadu
2016-07-08 17:41                 ` Dean Thompson
2016-07-08 17:49                   ` Yotam Barnoy
2016-07-08 17:28             ` Duane Johnson
2016-07-09 13:46             ` Ashish Agarwal
2016-07-09 13:51               ` Gabriel Scherer
2016-07-09 14:13                 ` Dean Thompson
2016-07-09 17:29                   ` Duane Johnson
2016-07-10 14:03                     ` Gabriel Scherer
2016-07-10 14:25                       ` Yotam Barnoy
2016-07-10 14:29                         ` Jesse Haber-Kucharsky
2016-07-10 14:34                           ` Gabriel Scherer
2016-07-10 14:47                             ` Yotam Barnoy
2016-07-10 16:45                               ` Glen Mével
2016-07-10 16:59                                 ` Yotam Barnoy
2016-07-10 18:40                                   ` Yotam Barnoy
2016-07-10  3:06                 ` Yotam Barnoy
2016-07-10  2:32               ` Yotam Barnoy
2016-07-10 19:17                 ` Ashish Agarwal
2016-07-08 19:16         ` [Caml-list] Getting the word out Hendrik Boom
2016-07-08 20:51           ` moosotc
2016-07-08 22:48             ` Hendrik Boom
2016-07-08 20:57           ` Steven Shaw
2016-07-08 21:13             ` Duane Johnson
2016-07-08 22:54               ` Yotam Barnoy
2016-07-08 23:11                 ` Duane Johnson
2016-07-09 13:13                   ` Ashish Agarwal
2016-07-08 22:02           ` SP
2016-07-08 21:56         ` [Caml-list] how to encourage adoption of OCaml? SP
2016-07-08 22:18           ` Fabrice Le Fessant
2016-07-08 22:39             ` Duane Johnson [this message]
2016-07-08 23:00               ` Yotam Barnoy
2016-07-09 13:03             ` Armaël Guéneau
2016-07-09 13:42               ` Dean Thompson
2016-07-08 21:46       ` SP
2016-07-08 22:05         ` Robert Muller
2016-07-08 23:11           ` Gerd Stolpmann
2016-07-09  1:37             ` Markus Mottl
2016-07-09 22:19               ` Yaron Minsky

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=CAFLokDdctXZD_URH_mKDA98h4+Sbdb0OneA8A464OHtwBSg2EA@mail.gmail.com \
    --to=duane.johnson@gmail.com \
    --cc=Fabrice.Le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=deansherthompson@gmail.com \
    --cc=gabriel.scherer@gmail.com \
    --cc=sp@orbitalfox.com \
    /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).