From: Adrien Nader <adrien@notk.org>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Mon, 13 Jan 2014 23:30:21 +0100 [thread overview]
Message-ID: <20140113223021.GA30935@notk.org> (raw)
In-Reply-To: <CAPFanBFZM5+-u9tDd1eSpVN2jzEYwDijiu109VoOLPteEfkyBQ@mail.gmail.com>
On Mon, Jan 13, 2014, Gabriel Scherer wrote:
> On Mon, Jan 13, 2014 at 12:14 PM, Daniel Bünzli
> <daniel.buenzli@erratique.ch> wrote:
> > 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.
>
> This is a bit too snarky for me to guess what you want.
>
> I'm already doing a few reviews on mantis, and occasionally uses the
> github in-patch-commenting interface when people send a link to a
> github-hosted patch (eg. http://caml.inria.fr/mantis/view.php?id=6274
> ). I would be ready to experiment with a mailing-list or a specialized
> review tool, based on what people would prefer. We have a solid github
> mirror in place ( github.com/ocaml/ocaml ), people of OCamllabs have
> kindly offered to host mailing-lists on several occasions, and have
> experimented with, for example, gitlab in the past.
>
> People of the list, if you have sent or reviewed patches or consider
> doing so in the future, do you have a strong preference? If your
> peer/friend/colleague wishes to contribute and asks you the place to
> go, what will you wish we had?
>
> (Keep in mind that we don't have a lot of patches sent around for now
> (less than a dozen a month), and even less people*time to do the
> reviews, so we don't necessarily need a highly tuned über-process.)
Reducing reviewer work and/or having more reviewers was the actual goal
behind my proposal.
Another core aspect is that setting up a mailing-list and putting up a
"howto contribute" page takes a few minutes of work unlike migrations of
whole systems or the use of forges(*).
I was also not thinking of replacing patches and reviews on mantis, more
having an additional tool to conduct code review although, of course, I
would prefer a single place for that. In any case, having something
agreed upon and documented is probably what matters most.
On a personal note, I also prefer getting fed with emails for which I
will use a decent client with an editor I enjoy rather than a web
browser (especially when there's flash on the pages).
(*) A word about phabricator too: it has some very nice things on paper
and on demo but I've found it makes things easier for frequent
users/devs and very bad for others
--
Adrien Nader
next prev parent reply other threads:[~2014-01-13 22:30 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
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 [this message]
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=20140113223021.GA30935@notk.org \
--to=adrien@notk.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