caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniil Baturin <daniil@baturin.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Mon, 17 Jan 2022 16:33:49 +0700	[thread overview]
Message-ID: <714c3a8d-25c8-c91e-ae01-46bf00920ffd@baturin.org> (raw)
In-Reply-To: <YeU09SJ52gUYJLyx@prajna.paris.inria.fr>

On 1/17/22 16:20, Sébastien Hinderer wrote:
> Sam Kuper (2022/01/16 14:31 +0000):
>> On Sun, Jan 16, 2022 at 09:40:20AM +0000, orbifx wrote:
>>>> For more specific help I encourage you to ask your question on
>>>> Discuss https://discuss.ocaml.org/
>>> Please keep the mailing lists going too, with people asking questions
>>> or having discussions here. Not just for announcements.
>> +1.
>>
>> Discourse (the service-as-a-software-substitute currently being used to
>> provide https://discuss.ocaml.org/ ) has some quite serious
>> accessibility flaws.  The more that discussions happen there instead of
>> on the mailing list, the less accessible the OCaml ecosystem is likely
>> to become.
> Being myself blind I feel very concerned about accessibility. I admin I
> didn't try the forum, but (1) all the forums I tried so far I ofudn way
> mess accessible than good old mailing lists and (2) yes, mailing lists
> are totally accessible and, in my opinion, very simple to use.
> Many thanks for promoting the accessibility concern!
>
> Sébastien.

Could you try the discuss.ocaml.org forum and share your opinion about 
its accessibility?

Discourse is NOT a service-as-a-software-substitute. It's free software 
distributed under GPLv2. See https://github.com/discourse/discourse
They provide managed hosting to fund its development and make life 
simpler for people who don't have the skill or time to maintain their 
own servers. Their managed hosting is also free of charge for FOSS projects.

Its accessibility _can_ be improved by the community.



  reply	other threads:[~2022-01-17  9:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:56 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:18 ` Nicolás Ojeda Bär
2022-01-16  9:40   ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:31     ` Sam Kuper
2022-01-17  9:20       ` Sébastien Hinderer
2022-01-17  9:33         ` Daniil Baturin [this message]
2022-01-17 14:30           ` Sam Kuper
2022-01-17 14:56             ` Daniil Baturin
2022-01-17 17:36               ` Sam Kuper
2022-01-17 21:06                 ` Gabriel Scherer
2022-01-18  1:51                   ` Sam Kuper
2022-01-19 15:46                     ` Sébastien Hinderer
2022-01-18  9:48                   ` orbifx
2022-01-18 15:55                     ` Simon Cruanes
2022-01-19 16:31                       ` Sébastien Hinderer
2022-01-19 17:51                         ` Sam Kuper
2022-01-19 18:09                           ` Sam Kuper
2022-01-19 19:09                             ` Sébastien Hinderer
2022-01-19 20:53                               ` Sam Kuper
2022-01-19 18:42                           ` Simon Cruanes
2022-01-19 19:03                           ` Sébastien Hinderer
2022-01-19 20:50                             ` Sam Kuper
2022-01-20 20:56                         ` Edwin Török
2022-03-11  8:46                           ` Sébastien Hinderer
2022-03-11  9:37                             ` Vasilis Goumas
2022-03-11  9:42                               ` Gabriel Scherer
2022-01-19 15:33                   ` Sébastien Hinderer
2022-01-19 21:43                     ` Gabriel Scherer
2022-01-19 22:01                       ` Sam Kuper
2022-01-19 22:38                         ` Sébastien Hinderer
     [not found]                 ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>
2022-01-17 22:47                   ` Sam Kuper
2022-01-17  9:53         ` Alan Schmitt
2022-01-17 13:52           ` Sam Kuper
2022-01-19 15:18             ` Sébastien Hinderer
2022-01-19 15:54           ` Sébastien Hinderer
2022-01-20  9:12             ` Alan Schmitt
     [not found]             ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:15               ` Sébastien Hinderer

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=714c3a8d-25c8-c91e-ae01-46bf00920ffd@baturin.org \
    --to=daniil@baturin.org \
    --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).