From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: orbifx <fox@orbitalfox.eu>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Sam Kuper <sampablokuper@posteo.net>,
caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Tue, 18 Jan 2022 15:55:13 +0000 [thread overview]
Message-ID: <Yebi4VyeVD5ts7FK@church> (raw)
In-Reply-To: <696b25b0-7567-0b1b-4203-9f53634ca998@orbitalfox.eu>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
I think there's a tension between the needs of people who are used to
30 years old mailing list software (like the GNU mailman) and the larger
number of people used to fancy UIs like discord. To the latter group,
discourse is barely "modern" enough; to the former, it's too
javascript-heavy.
By the way Sam, I opened https://discuss.ocaml.org/about in a TUI
browser and it looked kind of ok. I don't know about registration
though, it'd be good if there was a way to register purely by email to
make it more accessible. For the rest, _once registered_, as far as I'm
concerned, it's just a mailing list software. I don't have particular
accessibility needs so I'm probably oblivious to a lot of issues.
--
Simon Cruanes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-18 15:55 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
2022-01-19 15:46 ` Sébastien Hinderer
2022-01-18 9:48 ` orbifx
2022-01-18 15:55 ` Simon Cruanes [this message]
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=Yebi4VyeVD5ts7FK@church \
--to=simon.cruanes.2007@m4x.org \
--cc=caml-list@inria.fr \
--cc=fox@orbitalfox.eu \
--cc=gabriel.scherer@gmail.com \
--cc=sampablokuper@posteo.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).