caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Glen Mével" <glen.mevel@crans.org>
To: caml-list@inria.fr
Cc: Andreas Rossberg <rossberg@mpi-sws.org>
Subject: Re: [Caml-list] Discourse instance for the OCaml community? (was: how to encourage adoption of OCaml?)
Date: Sun, 10 Jul 2016 18:10:27 +0200	[thread overview]
Message-ID: <46ff9104-48ea-3fc7-da37-d3a1c6d147bc@crans.org> (raw)
In-Reply-To: <9445A645-1A01-4B74-8DB4-03C911DE3A06@mpi-sws.org>

[-- Attachment #1: Type: text/plain, Size: 3062 bytes --]

Andreas Rossberg a écrit (le 10/07/2016 à 09:21) :

> To paraphrase Dijkstra, IMHO email and mailing lists are an
> improvement over more “modern” forums in almost every way, once you
> get past the “flashiness” thing:
>
> - participation without having to constantly log into yet another
>   account (with potential tracking),
> - all communication through the same tool/UI (that actually works),
>   easy cross-communication and cross-quoting, archiving in one place,
>   etc
> - offline reading & writing,
> - proper threading (Discourse sees its lack as a “feature"),
> - no annoying gamification,
> - open, standardised and guaranteed to still be around in 5 or 10
>   years from now.

i fully agree with all this. however, there is one single feature that i
miss with email and newsgroup: the ability to edit a message after it
was sent. sadly, by the nature of those protocols this can’t be fixed,
and to me this is the single stuff that makes the web‐2.0‐based
solutions (forums and the like) unavoidable. [ other missing features,
available in more recent technologies, are either superfluous
(avatars?), or tied to contents (redaction in a Markdown‐like format,
syntax highlighting…), thus can be circumvented. ]

moreover, i second Anthony & others in saying that the mailing‐list
format somehow refrains people from participating. it may be good for
the essential discussions, but otherwise limits beginner questions and
general community exchanges.

plus the current mailing lists lack visiblity, as pointed out before.

for these reasons i believe too that a forum‐like solution may prove
valuable. it may allow discussions to grow freely, and as a side‐effect
would increase the visibility of the community.

to that purpose, Discourse may be the less bad solution, for it
	— being open‐source,
	— being well‐known, by which i mean that:
		(1) it is a modern, trendy solution that would refresh
		    the image of the community as depicted by Duane,
		    and may attract newcomers, [*]
		(2) the interface would look familiar,
	— gaining from a wider adoption more potential for becoming a
	  standard in lieu of the wild forum solutions, as a successor
	  for, say, newsgroups.
	— plus i see on its homepage than it can use OpenID, which
	  partially addresses your point about logging in (not the
	  tracking issue, though…).

the drawback is, as you pointed out, the absence of interoperability
with external clients and protocols (run a browser+JS or die). however,
as it is open‐source, it should be possible to ask for improvement of at
least the email gateway — even if a good email gateway still wouldn’t be
satisfying from that perspective. also note that Discourse apparently is
a mailing‐list manager too, so we may conveniently mirror this list in
our new forum; this would help avoiding community fragmentation as you
fear it.

-- 
Glen Mével

[*]: well, you should ask a more hype-sensitive person on that point.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-07-10 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 20:58 Gabriel Scherer
2016-07-10  7:21 ` Andreas Rossberg
2016-07-10 10:47   ` SP
2016-07-10 12:25     ` Anthony Tavener
2016-07-10 15:31       ` Dean Thompson
2016-07-10 13:53   ` Gabriel Scherer
2016-07-10 16:10   ` Glen Mével [this message]
2016-07-10 20:31     ` Hendrik Boom
2016-07-11  8:48       ` Stanislav Artemkin
2016-07-10 16:36 ` Armaël Guéneau

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=46ff9104-48ea-3fc7-da37-d3a1c6d147bc@crans.org \
    --to=glen.mevel@crans.org \
    --cc=caml-list@inria.fr \
    --cc=rossberg@mpi-sws.org \
    /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).