From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id D5C597FE44 for ; Sat, 9 Jul 2016 00:39:46 +0200 (CEST) IronPort-PHdr: 9a23:In21/R3Kk1QLky0usmDT+DRfVm0co7zxezQtwd8ZsegeLfad9pjvdHbS+e9qxAeQG96Ks7Qf0aGP7ujJYi8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL2PbrnD61zMOABK3bVMzfbWtXNWIxJ3qn8mJuLTrKz1SgzS8Zb4gZD6Xli728vcsvI15N6wqwQHIqHYbM85fxGdvOE7B102kvpT41NdZ/i9Ro/Ms8dJbGeW/JvxgDO8QMDNzHWk//szguFHnQEOh62AHW2MK2k5mCgLf7Rr3GLP8hSX3rfF03jWyPMvsTLlyVy70vIlxTxq9pDoOMTNx0mbXjNd3iuoPrA+ooRE5wYnUZpqSMtJxe6rceZURQm8XDZUZbDBIHo7pN9hHNOEGJ+sN6tCl/1Y= Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=duane.johnson@gmail.com; spf=Pass smtp.mailfrom=duane.johnson@gmail.com; spf=None smtp.helo=postmaster@mail-it0-f44.google.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of duane.johnson@gmail.com) identity=pra; client-ip=209.85.214.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="duane.johnson@gmail.com"; x-sender="duane.johnson@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of duane.johnson@gmail.com designates 209.85.214.44 as permitted sender) identity=mailfrom; client-ip=209.85.214.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="duane.johnson@gmail.com"; x-sender="duane.johnson@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-it0-f44.google.com) identity=helo; client-ip=209.85.214.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="duane.johnson@gmail.com"; x-sender="postmaster@mail-it0-f44.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0C6AAAhK4BXfyzWVdFchRAGrVqGM4UEgXqGGAKBIQc5EwEBAQEBAQEBEQEBCQsLCR8xgjKCGwEEARIRHQEbEgIJAQMBCwYFBAc3AgIiAREBBQEcBhMUBAqHcwEDDwihMYExPjGLO4FqgloFhWAKGScNUoNJAQEBAQEFAQEBAQEBARgCBhCGF4RNh0KCWgWOeIocgVqMdYFqiAaFPI5PEh6BDx8BhEQdMokyAQEB X-IPAS-Result: A0C6AAAhK4BXfyzWVdFchRAGrVqGM4UEgXqGGAKBIQc5EwEBAQEBAQEBEQEBCQsLCR8xgjKCGwEEARIRHQEbEgIJAQMBCwYFBAc3AgIiAREBBQEcBhMUBAqHcwEDDwihMYExPjGLO4FqgloFhWAKGScNUoNJAQEBAQEFAQEBAQEBARgCBhCGF4RNh0KCWgWOeIocgVqMdYFqiAaFPI5PEh6BDx8BhEQdMokyAQEB X-IronPort-AV: E=Sophos;i="5.28,332,1464645600"; d="scan'208,217";a="226131198" Received: from mail-it0-f44.google.com ([209.85.214.44]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 09 Jul 2016 00:39:44 +0200 Received: by mail-it0-f44.google.com with SMTP id f6so14818974ith.0; Fri, 08 Jul 2016 15:39:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7WriWUWFChYw3g4VmX/v/e+afx7LH3y73drbGXRSwHc=; b=qsb+WJMw/gtZrzq3vy69J5U7G8SJs2YDo4DQU585osYYJn+xqohwSK/8u1kJXgAvD0 POrvdEKw9VX4V7NqBeBySYHX4Ovxc3ObQIJwIXnelx7LZOyYpjvUE3Y56Esugk990c/T ayL6mQm0honNM04C9rDYoffhA0pkNWBcKc+b8e1t1bnuAIgMBvEDRpdH6236iL0amR72 TMmnaxDcmv6uq+wWNAaAn5xEAJm3TwmAr21G6Q+VP+a2QmJCcV9/x2CKrf0KXzOVe8rs itaG4DlbphfIY6h1xxwGhNdNJuMS8onxOM0vwku88vOslgB8UUjFe0R/QzLOgwEUGKW5 nCZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7WriWUWFChYw3g4VmX/v/e+afx7LH3y73drbGXRSwHc=; b=a3HsLLk/FWpREfeEGn4dk6/eCFkIvJHrNJVbRrWsFAoQhx5PdAesFbghI5slBlC/gj /HrJyYC6k846JOoTLt+mR2VjjODH8C6FQyql2PkcqUQKtRGDhi7FpoxXOQW/tUiUggKH mu/CZtCkAmRsM8Gr4xIQRd5UD5zrIinyXo7Owid85zbfGP8h/jsgkPCiX3KT7CmnUWKW YRZiSs6KyAV664uSpZov36IYGJiTLJwiCKxHbX3XUpBdDLs/SRwEbqTbUxve2LoLWuu0 5lH1dcue5eFQziXFaJFE3R9nNt55Pks28F27n0u6WVKUG7bem+k/GbxK1aewrAJA54q7 VjaA== X-Gm-Message-State: ALyK8tIvkBxjArOUUZUJXfo4yqAR2u6lUCwiu6yNwDPBVzp8WxWyb44GyfbtPPuQOO81QOGu9w4KG5Mt3vfutw== X-Received: by 10.36.26.194 with SMTP id 185mr951900iti.28.1468017582941; Fri, 08 Jul 2016 15:39:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.59.228 with HTTP; Fri, 8 Jul 2016 15:39:42 -0700 (PDT) In-Reply-To: References: <20160704144512.GB2458@Razor> <20160708215630.GC1723@tiger> From: Duane Johnson Date: Fri, 8 Jul 2016 16:39:42 -0600 Message-ID: To: Fabrice Le Fessant Cc: SP , Gabriel Scherer , Dean Thompson , "caml-list@inria.fr" Content-Type: multipart/alternative; boundary=001a1143e2b28e552b0537277ae5 Subject: Re: [Caml-list] how to encourage adoption of OCaml? --001a1143e2b28e552b0537277ae5 Content-Type: text/plain; charset=UTF-8 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. --001a1143e2b28e552b0537277ae5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Jul 8, 2016 at 4:18 PM, Fabrice Le Fessant <Fabrice.Le_f= essant@inria.fr> wrote:
Any= way, I am not fond of the multiplication of communication channels, they te= nd 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 d= iscussions 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 mi= ght 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 ev= erything 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 twi= tter users (at that time I had only started following a handful) and I real= ized something different was going on--this wasn't a medium where I cou= ld drink in every tweet, it was a firehose and I could come get splashed he= re and there when I wanted to :)

I = think there's a place for less consequential announcements and discussi= ons in a community--especially a large one. Important information will almo= st always reach critical mass and the network will distribute it to every l= eaf node. A mailing list is a good solid place for discussion, and every in= coming 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&= #39;s too much noise.

When the Hask= ell mailing list experienced this kind of growth, there was someone in the = community who took it upon themselves to summarize the important announceme= nts, events, and projects that had taken place in the past week. People cou= ld 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 even= ts.

Perhaps someone could do the sa= me, as a bridge between the github and caml-list groups.
--001a1143e2b28e552b0537277ae5--