caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] how to encourage adoption of OCaml?
Date: Sun, 10 Jul 2016 14:40:42 -0400	[thread overview]
Message-ID: <CAN6ygO=f8VR_8Rkz4v9_QQ-cJoaXDoW1Jm4cbed-JGu5SCgJ_Q@mail.gmail.com> (raw)
In-Reply-To: <CAN6ygOnbi2DDw+k4qVyccAXLUe=xfnFn=pWRG_hKNqmCcGZMxg@mail.gmail.com>

Gabriel, I surveyed a few of the IRC lurkers. The sense I get from
their reactions is that they wouldn't want to leave IRC (which makes
sense) but would be open to a gitter room that connected to IRC via a
bridge.

This means that to establish the gitter room + bridge we need to:
1. Create the gitter room on the gitter site. This must be done by
someone with OCaml github credentials.
2. Follow the instructions on
https://github.com/matrix-org/matrix-appservice-gitter using an OCaml
server. The bridge must have access to github credentials as well.
3. Add the new room to the ocaml.org community page. Involves a simple PR.

On Sun, Jul 10, 2016 at 12:59 PM, Yotam Barnoy <yotambarnoy@gmail.com> wrote:
> I just asked on the neovim gitter, and the service they use to bridge
> with IRC is this one:
> https://github.com/matrix-org/matrix-appservice-gitter
>
> Every aspiring programmer has a github account at this point. It's
> just reality. Even without one, you get to view gitter chat in
> realtime. IRC requires a bunch of extra arcane knowledge that most
> beginners aren't willing to learn, to a large degree because IRC is
> simply not being used actively anymore.
>
> Listen -- you can always dismiss features, and like I said,
> programmers tend to believe that what they use is the best and
> everything new or different is unnecessary. I get it -- I think like
> that automatically as well. I think we have to look beyond that --
> many of the advantages of new technologies seem minor but they add up.
> People were giving the same kinds of rebuttals to moving to github
> before that move was made (though I don't think the improvement will
> be anywhere near that delta).
>
> Perhaps the key thing to grasp here is this: we're competing with
> other languages and ecosystems for programmers. We need to be as
> attractive as possible. This competitiveness must take into account
> knowledge of the current tools and the impressions they leave on
> users. As soon as there's a hurdle in the way, many potential
> newcomers will be lost. The additional benefits to existing community
> members are there as well, but they're harder to talk about tangibly
> until we experiment with the new communication channels.
>
> On Sun, Jul 10, 2016 at 12:45 PM, Glen Mével <glen.mevel@crans.org> wrote:
>> Yotam Barnoy a écrit (le 10/07/2016 à 16:47) :
>>
>>> […] I've found gitter to be ideal for this, much more so than IRC
>>> (which has a high barrier-of-entry).
>>
>> what is so complicated about using the web interface to IRC [1] ?
>>
>> what about the barrier‐of‐entry to that gitter? i’ve never heard of it
>> before and i’m not sure what’s so new there (apart from the built‐in
>> persistence), but as i understood, it is a github service so it would
>> require a github account (and to accept to be publicly linked to that
>> github account, and to rely on proprietary solutions, etc·), whereas IRC
>> requires nothing.
>>
>>> I'll enquire on IRC (just connecting requires me using an annoying
>>> service like IRCCloud, which shows the problem -- I can't even post
>>> the question and get a notification about a response.)
>>
>> at least the web interface mentionned above does notify you, and even
>> plays a sound iirc. if you are not served within the hour and want to
>> stay 24 hours a day to finally see your answer, then structured forums
>> are better fit to your use than messy instant messaging anyway.
>>
>> --
>> Glen Mével
>>
>> [1]: http://webchat.freenode.net/?channels=#ocaml
>>
>> p·s·:
>>
>>> b. there are tools to scrape gitter history in existence, making the
>>> fact that they're proprietary fairly irrelevant.
>>
>> the point about proprietary systems is not a mere matter of retrieving
>> history…
>>

  reply	other threads:[~2016-07-10 18:41 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 [this message]
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
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='CAN6ygO=f8VR_8Rkz4v9_QQ-cJoaXDoW1Jm4cbed-JGu5SCgJ_Q@mail.gmail.com' \
    --to=yotambarnoy@gmail.com \
    --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).