From: Anil Madhavapeddy <anil@recoil.org>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Marshall <marshall@logical.net>, caml users <caml-list@inria.fr>,
infrastructure <infrastructure@lists.ocaml.org>
Subject: Re: [Caml-list] discuss.ocaml.org now available
Date: Mon, 15 May 2017 22:33:23 +0800 [thread overview]
Message-ID: <AEE094E7-578B-425B-A83F-28FAF5C58263@recoil.org> (raw)
In-Reply-To: <m2zieegsk1.fsf@charm-wifi.irisa.fr>
On 15 May 2017, at 21:26, Alan Schmitt <alan.schmitt@polytechnique.org> wrote:
>
> Hello,
>
> "AM" == Anil Madhavapeddy <anil@recoil.org> writes:
>
> AM> Therefore, I have set up a hosted Discourse instance at
> AM> http://discuss.ocaml.org as an experimental service, and now need
> AM> your help to decide whether or not this is a viable longer term
> AM> solution for our community.
>
> I don't know if I'll have the time to monitor this to include in the
> Caml Weekly News (at the moment I include material from this list, from
> the github pull requests (which I receive automatically by mail), and
> from the ocaml.org planet aggregation). Do you think I should include
> the discussions there in the CWN, and if so can I easily interact with
> Discourse using email?
An excellent question -- it seems unfair to burden you with monitoring
yet another forum for the CWN.
Would anyone be willing to summarise some of the more interesting
threads from discuss.ocaml.org and forward a summary to Alan?
It may also be possible to script this up with the http://docs.discourse.org
web API to get a list of titles and URLs, but I expect that it would still need
someone to edit it into a more succinct form for you to include on CWN.
Also, would it also be useful to cross-post CWN to discuss.ocaml.org?
I believe it is possible to generate new posts directly via e-mail, so this
should just involve you CCing a new address. I haven't quite figured out
how this works yet, but will do soon if there's interest...
If you (or anyone else) wants to interact with discuss.ocaml.org via
email only, there is a "mailing list mode" you have to activate, and then
everything shows up in your inbox as multipart email (html and plaintext
markdown, suitable for mutt).
See this: https://discuss.ocaml.org/t/email-subscription/137
for the question about it on the forum.
regards,
Anil
next prev parent reply other threads:[~2017-05-15 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 17:22 [Caml-list] Change policy on beginners list? 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
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 [this message]
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
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=AEE094E7-578B-425B-A83F-28FAF5C58263@recoil.org \
--to=anil@recoil.org \
--cc=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=infrastructure@lists.ocaml.org \
--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