From owner-freebsd-current@FreeBSD.ORG Mon Jul 11 23:23:11 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12824106566C; Mon, 11 Jul 2011 23:23:11 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A41188FC13; Mon, 11 Jul 2011 23:23:10 +0000 (UTC) Received: by qwc9 with SMTP id 9so2824477qwc.13 for ; Mon, 11 Jul 2011 16:23:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=eQFgrA3s07/VmwNk6Q0mEgcmlmz5x+HI0zRSnzYUM00=; b=F9PAjYh2sfdWhDS8BW3nGBzXai+IGlaLVvf7cJfs1AXE4NC6LuX8i3L5pv+d3HhwMj mj70RiFBnh6/RKyZKux+C/n1Uh0gVoF1vEna2EM9QbtC/BNpvq33cq3su92xXpdDRvEN 2P8CY51Ss2vRdJLVjOg4cDU2Lg4sY/lgmXt3o= MIME-Version: 1.0 Received: by 10.229.1.67 with SMTP id 3mr4110907qce.150.1310425216521; Mon, 11 Jul 2011 16:00:16 -0700 (PDT) Received: by 10.229.37.12 with HTTP; Mon, 11 Jul 2011 16:00:15 -0700 (PDT) In-Reply-To: References: <4E1421D9.7080808@zedat.fu-berlin.de> <4E147F54.40908@zedat.fu-berlin.de> <20110706162811.GA68436@troutmask.apl.washington.edu> <20110706193636.GA69550@troutmask.apl.washington.edu> <4E14CCE5.4050906@zedat.fu-berlin.de> <20110707015151.GB71966@troutmask.apl.washington.edu> <4E1B67C7.8040402@FreeBSD.org> Date: Mon, 11 Jul 2011 16:00:15 -0700 Message-ID: From: Ali Mashtizadeh To: Arnaud Lacombe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current , Andriy Gapon Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 23:23:11 -0000 Maybe someone can setup something like reviewboard [1] for developers to use. This may also help folks who want to keep abreast of the current work in a particular subsystem or get involved into the development process more. At my company we use reviews and it seems to help the catch some bugs and help new engineers ramp up faster. [1] http://www.reviewboard.org/ ~ Ali On Mon, Jul 11, 2011 at 2:48 PM, Arnaud Lacombe wrote: > Hi, > > On Mon, Jul 11, 2011 at 5:14 PM, Andriy Gapon wrote: >> on 11/07/2011 23:33 Arnaud Lacombe said the following: >>> For the record, I would like to see enforced public review for _every_ >>> patch *before* it is checked in, as a strong rule. gcc system is >>> particularly interesting. But it is not likely to happen in FreeBSD >>> where FreeBSD committers are clearly more free than other at >>> checking-in un-publicly-reviewed stuff (especially _bad_ stuff). >>> >>> This would of course apply even to long-time committers, no matter how >>> it hurt their ego (which I definitively do not care about). >> >> Have you just volunteered to review all of the patches that I would like= to >> commit? =C2=A0And are you prepared to take responsibility for quality of= your reviews? >> I am sure that other developers will gladly accept your offer too. >> > _No-one_ can do all the reviews, especially not me (on a purely > technical level). ACK must come from subsystem maintainers. Having > public review would allow the community review, which is now just not > possible today. As about patches from the maintainer, they might be > committed without his approval, but still sent for review. If a > maintainer goes outside his area, he has to get approval from the > other subsystem maintainer. > > =C2=A0- Arnaud > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >