From: Sam Kuper <sampablokuper@posteo.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Tue, 18 Jan 2022 01:51:10 +0000 [thread overview]
Message-ID: <20220118015110.w36uavob7fuw4vkk@posteo.de> (raw)
In-Reply-To: <CAPFanBG5eR-uFpQwd-73yRkmCxUdiYgzO4JS+ggBRM__rDey4Q@mail.gmail.com>
On Mon, Jan 17, 2022 at 10:06:51PM +0100, Gabriel Scherer wrote:
> With my OCaml Foundation hat on, let me give credit where credit is
> due: the Foundation wasn't actually involved in creating or
> maintaining the Discourse forum. It was an initiative of Anil
> Madhavapeddy,
Fair enough.
> and the list of administrators and moderators is publicly available:
> https://discuss.ocaml.org/about
Alas, only in an accessibility-limited way - i.e. not to everybody.
> The fact that Discourse offers hosting for the forum reduces the
> administration work quite a bit. We may not have this forum at all if
> we had decided that self-hosting was a requirement.
Indeed.
OTOH, the advantage of not having the forum would be that more
discussions would have happened on the mailing list, instead of being
fragmented into a different, accessibility-limited silo.
> I don't personally have a strong opinion on whether the usage of
> forums is a good or bad thing,
See below for a reason to have such an opinion, at least re: forums with
accessibility issues such as those powered by Discourse.
> but I can only remark that while some people are more comfortable with
> the mailing-list (or forced to use them for accessibility reason,
> which is not the same thing at all), some other people are not
> comfortable with mailing-lists anymore.
You seem to acknowledge that:
- mailing lists are accessible (score: ~1 point for accessibility),
and are also comfortable for some though not all users (score: ~0.5
points for comfort); whereas
- Discourse is not accessible for all users (score: ~0.5 points for
accessibility), and is comfortable for some though not all users
(score: ~0.5 points for comfort).
On this analysis, then, mailing lists score higher overall, especially
if accessibility is given extra weighting (as, IMO, it should be).
As mentioned earlier, the existence of a forum alongside a mailing list
tends to divert some traffic from the mailing list (where it is
accessible) to the forum (where it may not be - depending on the forum
software).
Taken together, these facts allow the conclusion that the usage of
not-universally-accessible forums, alongside or instead of mailing
lists, is a bad thing.
> [..] If you know people who would be willing to work on improving the
> accessibility of Discourse, we should think about funding this work.
> Please get in touch!
That is very good of you - thank you.
If anyone reading this is available for that work, or knows someone who
is, then I hope they will take you up on that offer.
Best wishes,
Sam
--
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?
() ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
next prev parent reply other threads:[~2022-01-18 1:51 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
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 [this message]
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=20220118015110.w36uavob7fuw4vkk@posteo.de \
--to=sampablokuper@posteo.net \
--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