caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain.frisch@lexifi.com>
To: Yotam Barnoy <yotambarnoy@gmail.com>,
	Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Recent hooks design and general github PR issues
Date: Tue, 19 Jul 2016 22:21:14 +0200	[thread overview]
Message-ID: <20f0b337-2935-5a20-4aa6-642758648d55@lexifi.com> (raw)
In-Reply-To: <CAN6ygOn7DQw35jTRxHFda5keLFgfJ7rE3dBQ7ezNJarK8L2rxg@mail.gmail.com>

On 19/07/2016 17:08, Yotam Barnoy wrote:
> It may also be worthwhile to say that except for rare exceptions
> (mostly bug fixes), PRs should not be merged by the same person who
> authored them, as this makes the process seem biased and questionable.

Open source projects have leaders (Xavier and Damien, for OCaml), and 
other core maintainers with more decision power than the community.  And 
in the community, the opinions of some people have more weight than 
those of others.  Of course, the process is biased!

But compare to the situation before the switch to Git and GitHub: new 
developments were almost always pushed/committed by the author if they 
had commit rights, sometimes discussed (well, usually evoked) on 
caml-devel before, and even less often on Mantis.

The new situation is much more open and the level of review has 
increased significantly.  When someone with commit rights submits a PR, 
this is more community-friendly than pushing directly to trunk (which is 
not forbidden, and still happens), even if the same person finally does 
the merge after taking comments (from everyone) into account.  Possibly 
nobody feels like commenting, reviewing, nor endorsing the proposal; 
this is not ideal, but I don't think this should prevent merging after a 
reasonable amount of time, preferably also after mentioning the imminent 
merge.


Alain

  parent reply	other threads:[~2016-07-19 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 15:08 Yotam Barnoy
2016-07-19 15:36 ` Fabrice Le Fessant
2016-07-19 16:23   ` Yotam Barnoy
2016-07-19 17:28     ` Fabrice Le Fessant
2016-07-19 20:21 ` Alain Frisch [this message]
2016-07-21 12:09   ` Goswin von Brederlow
2016-07-21 12:38     ` Fabrice Le Fessant
2016-07-21 13:37       ` Hendrik Boom

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=20f0b337-2935-5a20-4aa6-642758648d55@lexifi.com \
    --to=alain.frisch@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=yotambarnoy@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).