From owner-freebsd-current@FreeBSD.ORG Sun Jul 17 11:54:57 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 2D4791065746; Sun, 17 Jul 2011 11:54:57 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id AA4648FC18; Sun, 17 Jul 2011 11:54:56 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.4/8.14.4) with ESMTP id p6HBstbl036448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 17 Jul 2011 13:54:55 +0200 (CEST) (envelope-from uqs@spoerlein.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net; s=dkim200908; t=1310903695; bh=741/M3Mg7vpn/oZV3PE7tPAypUPHoElfVhSLvnyKRW4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=PCJarXtf/rF0gtGiLhO6Ht/fqXcRzJdyJt4bw9Dw/RbrXjyeRAbXqnJxKsFgPsrIb SiS3YpRWYjtyJyiYDLDnCktHAtV3xXj1B4BicqFWhfldSsX8kd48vdNHqY4X19gYqF i/ArEJE7Rpe1pP37XMZ8Dy7BrJf1WX+9RC6NcnCk= Date: Sun, 17 Jul 2011 13:54:54 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Gleb Kurtsou Message-ID: <20110717115454.GG8485@acme.spoerlein.net> Mail-Followup-To: Gleb Kurtsou , mdf@freebsd.org, Ali Mashtizadeh , FreeBSD Current , Arnaud Lacombe References: <20110707015151.GB71966@troutmask.apl.washington.edu> <4E1B67C7.8040402@FreeBSD.org> <20110712214049.GA12290@tops> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110712214049.GA12290@tops> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mdf@freebsd.org, Ali Mashtizadeh , FreeBSD Current , Arnaud Lacombe 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: Sun, 17 Jul 2011 11:54:57 -0000 On Wed, 13.07.2011 at 00:40:49 +0300, Gleb Kurtsou wrote: > On (11/07/2011 16:36), mdf@FreeBSD.org wrote: > > On Mon, Jul 11, 2011 at 4:00 PM, Ali Mashtizadeh wrote: > > > 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/ > > > > FreeBSD development is completely open; anyone can sign up for the > > svn-src-* mailing list they are interested in, including > > svn-src-head@. Code reviews are plenty as well; just check the list > > archives for discussion of bugs, poor design choices and unintended > > effects. But most reviews are silent and after-the-fact by looking at > > the list mail. It's a system that seems to be working just fine for > > the FreeBSD project so far. This isn't a job for most anyone; it's a > > volunteer project and so anything that raises the barrier to getting > > work done for the project should be looked at with skepticism. > > I agree with everything said above and think that it's not reviews > that's missing. By review I don't mean something like getting "ok to > commit" reply from N developers before committing. svn-src@ works > great for it, commits keep getting reverted :) Review is a time > consuming process that also requires certain level of expertise. > Volunteer project can hardly afford it. > > Having a project adopted way of sharing work in progress will be a step > forward. Yes, I'm aware of perforce, it's to hard to use and wasn't > designed to share and test ideas. I think guthub can be a very good > candidate (but AFAIK it won't allow hosting of FreeBSD repo for not paid > accounts). I'm not suggesting switching to git as VCS, but using github > UI for communication and tracking not yet commited or work in progress > changes. In ideal world developers will merge patches from each other > increasing chance of a good code to survive and get commited later. > Currently we have patches hosted at people.freebsd.org, as attachments > on maillists and PRs -- almost all stale or outdated. Key difference of > github is that original patch author will be aware of you using it, > potentially updating and improving it. Others can continue supporting > the patch if original author abandons it, etc. Sending patches is too > complicated and counterproductive comparing to github. Yes, I fully agree, that's why https://github.com/freebsd/freebsd-head exists today, but hasn't been advertised yet (I need to write documentation and can't force myself to do it :( Feel free to start using it! Together with the git-svn metadata that you can grab from repos.freebsd.your.org it makes a solid platform for working on FreeBSD code. Uli