caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
	Hongbo Zhang <hzhang295@bloomberg.net>,
	marshall@logical.net, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Change policy on beginners list?
Date: Thu, 11 May 2017 20:38:25 +0100	[thread overview]
Message-ID: <7CC1A434-6814-484D-A2F8-8E9B5BC6C260@recoil.org> (raw)
In-Reply-To: <7B2C5D230E264432A259D91C0F5D7096@erratique.ch>

On 11 May 2017, at 20:19, Daniel Bünzli <daniel.buenzli@erratique.ch> wrote:
> 
> On Thursday, 11 May 2017 at 20:10, Gabriel Scherer wrote:
>> I would be happy to keep contributing with an email-based workflow,
> 
> What about http://lists.ocaml.org/ ? 

We can create a beginners list there very easily on request (infrastructure@lists.ocaml.org).

One other option that I can arrange to setup is Discourse (discourse.org), which is an open-source forum with a nice e-mail gateway (so it can be used purely in email based mode as well).  Quite a few open source projects use it as a good method of asynchronous communication.

There is a hosted version that I can arrange to be installed on a ocaml.org subdomain, but I will need at least a couple of volunteers to create categories and act as administrators for the site.

An advantage of such a Discourse-based forum is that it should be possible for OCaml library authors to easily create categories on the same forum to direct users of their software to, with minimal reconfiguration required. It would be great to have an area for those (e.g.) interested in JavaScript compilation to go to.

To see an example of Discourse in action, the Rust user forum is one good example: https://users.rust-lang.org.

regards,
Anil

  reply	other threads:[~2017-05-11 19:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 17:22 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-05-11 18:10 ` Gabriel Scherer
2017-05-11 19:19   ` Daniel Bünzli
2017-05-11 19:38     ` Anil Madhavapeddy [this message]
2017-05-11 20:14       ` Christophe Troestler
2017-05-11 20:26         ` Gabriel Scherer
2017-05-11 20:44           ` Runhang Li
2017-05-12  1:08             ` Marshall
2017-05-12  1:45               ` Pierpaolo Bernardi
2017-05-13 11:48               ` [Caml-list] discuss.ocaml.org now available Anil Madhavapeddy
2017-05-13 12:53                 ` SP
2017-05-15 14:37                   ` Anil Madhavapeddy
2017-05-15 15:13                     ` Gabriel Scherer
2017-05-17  0:17                     ` SP
2017-05-13 17:08                 ` Marshall
2017-05-15 13:26                 ` Alan Schmitt
2017-05-15 14:33                   ` Anil Madhavapeddy
2017-05-16  6:25                     ` Alan Schmitt
2017-06-05 15:33                 ` [Caml-list] [ocaml-infra] " Daniel Bünzli
2017-05-13 12:51 ` [Caml-list] Change policy on beginners list? SP
  -- strict thread matches above, loose matches on Subject: below --
2017-05-11 16:09 Marshall
2017-05-11 19:58 ` Hendrik Boom
2017-05-11 20:01   ` Hendrik Boom
2017-05-11 20:29 ` Oliver Bandel
2017-05-11 20:30 ` Oliver Bandel

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=7CC1A434-6814-484D-A2F8-8E9B5BC6C260@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=gabriel.scherer@gmail.com \
    --cc=hzhang295@bloomberg.net \
    --cc=marshall@logical.net \
    /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).