caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: "François Bobot" <francois.bobot@cea.fr>,
	"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Mon, 13 Jan 2014 12:14:12 +0100	[thread overview]
Message-ID: <E4B0C895D5F24EA5BAB5F3A05D87D2D5@erratique.ch> (raw)
In-Reply-To: <CAPFanBGE-Ey8pmG_cnpCWO_xCosNO0pUQunw8O4wS0ugGU4tSg@mail.gmail.com>

Le lundi, 13 janvier 2014 à 11:27, Gabriel Scherer a écrit :
> -- to lower the participation cost for those that are too cool to use
> a bug tracker of the previous decade.  

That's a troll. What some of us are asking for is a usable bugtracker (cf. #6052). Frankly, mantis doesn't even know how to properly escape markup when you are commenting issues. Having proper ways to introduce code (and, less essential, lightweight formatting) on a bugtracker seems an essential feature to me and that's just one example, I won't even talk about having a quick look at patches that you can't even see in context but will download to your computer. If you want to use broken and inhumane software it's your problem but don't try to label those that actually prefer usable software as being attracted by cool and shiny things.

> The nice thing with mailing-list is that they have easy-to-browse
> archives,  

It's not only easy to browse, it's *great* to browse: all the web-based mailing list archives I interact with are not even able to follow a thread running across two month. I really feel we're in 2014.  
  
> (about Github, a Wise One
> remarked that "yesterday the same people were commanding that we host
> OCaml on Sourceforge; look where it is now!").  

Sure, if you move to that kind of (free or paid) service always factor in the costs of entering and leaving it, as it certainly won't help you forever. What's forever anyways ?  
  
> I'm not personally afraid of having several places where patches are
> proposed

I think that's a rather bad idea.  

Daniel  

P.S. Since you mentioned gitlab et al, I was recently pointed to this aswell: http://phabricator.org/ never interacted with though.

  reply	other threads:[~2014-01-13 11:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 15:23 Adrien Nader
2014-01-11 15:41 ` Simon Cruanes
2014-01-13  9:04   ` Adrien Nader
2014-01-13  9:51     ` François Bobot
2014-01-13 10:27       ` Gabriel Scherer
2014-01-13 11:14         ` Daniel Bünzli [this message]
2014-01-13 13:26           ` Gabriel Scherer
2014-01-13 13:43             ` Thomas Refis
2014-01-13 13:51               ` Gabriel Scherer
2014-01-13 13:57               ` Simon Cruanes
2014-01-13 15:03                 ` Török Edwin
2014-01-13 13:58               ` Kakadu
2014-02-17 22:55                 ` Richard W.M. Jones
2014-01-13 13:57             ` Daniel Bünzli
2014-01-13 22:30             ` Adrien Nader
2014-01-13 22:39               ` Simon Cruanes
2014-01-13 23:09                 ` Adrien Nader
2014-01-14 11:13             ` Gabriel Kerneis
2014-01-14 13:23               ` François Bobot
2014-01-14 13:27                 ` Thomas Gazagnaire
2014-01-14 14:06                   ` Markus Mottl
2014-01-14 14:12                     ` Simon Cruanes
2014-01-14 14:55                       ` Amir Chaudhry
2014-01-14 15:09                       ` François Bobot
2014-01-14 15:11                         ` Anil Madhavapeddy
2014-01-13 16:42         ` Yotam Barnoy

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=E4B0C895D5F24EA5BAB5F3A05D87D2D5@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=francois.bobot@cea.fr \
    --cc=gabriel.scherer@gmail.com \
    /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).