caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Mon, 13 Jan 2014 10:04:44 +0100	[thread overview]
Message-ID: <20140113090444.GA8904@notk.org> (raw)
In-Reply-To: <20140111154146.GA976@lenat>

On Sat, Jan 11, 2014, Simon Cruanes wrote:
> Le Sat, 11 Jan 2014, Adrien Nader a écrit :
> > Hi,
> > 
> > (and sorry for the mail sent a few minutes ago :) )
> > 
> > I'd like to know what people think about having a mailing-list for
> > reviews and tests of patches to the compiler and tools around it.
> > 
> > The idea is to do something similar to the kernel mailing-list. I mostly
> > like mantis and it is possible to attach files but it becomes fairly
> > unreadable after a while. The audience is also mostly limited to people
> > who are subscribed to the bug report. I hope this reduces the work and
> > burden of reviewers and especially commiters.
> > 
> > The goal is not to replace patches on mantis and you shouldn't believe
> > this has been blessed by the core development team (nor mentionned to
> > them actually). Instead, I hope this helps do quicker (and smaller?)
> > iteration of patches.
> > 
> > One example where I believe this would be useful is for the
> > cross-compilation patches I've started getting upstreamed around one
> > year ago. There are still many patchs which touch many files and
> > definitely need tests on platforms I don't usually run.
> > 
> > Another case is for patches which touch bits of the compiler almost
> > no-one is familiar with; I think this could help get more input.
> > 
> > Rules would be similar to http://linux.yyz.us/patch-format.html but less
> > strict (that is also mostly something to begin with).
> > In addition, there should be no specific reviewer or set of reviewers
> > for a given component; it is also known, acknowledged and perfectly fine
> > that the available time of reviewers varies. In practice this means you
> > should not refrain from commenting on a patch because someone else
> > usually handles a given topic.
> > 
> > Of course, this requires two things: a bit of infrastructure (I hear
> > it's much easier to create mailing-lists on ocaml.org than on inria's
> > servers), and people (i.e. you). Anyone interested and willing to
> > participate?
> 
> The idea is nice. I don't know the compiler's internals and would
> certainly be interested in being familiar with them. Is a new mailing
> list necessary - do you envision massive traffic on the list - or could
> the current ocaml list, which is usually quite quiet, be used for
> compiler discussions?

I don't think there would be massive traffic but probably some bursts
(especially when there are 10 patches or more in a series) and that
could be annoying to some.

Also, I'd say the caml-list actually has some traffic on it.

> The parallel with the recent suggestion to host wikis on ocaml.org to
> centralize information about how to do parallelism (or other
> similar topics regarding the high-level use of OCaml) may be interesting.
> Would a small-ish wiki about the compiler and compiler's hacking be
> useful? Can a mailing-list play the same role as a wiki?

Well, I don't know compiler internals very well either so it's difficult
for me to say. However having information on how to contribute back (be
it a wiki page or a static page updated through git) would definitely be
useful as there is a growing number of people asking for such infos (at
least on IRC on #ocaml).

-- 
Adrien Nader

  reply	other threads:[~2014-01-13  9:04 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 [this message]
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
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=20140113090444.GA8904@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;
as well as URLs for NNTP newsgroup(s).