From owner-freebsd-current@FreeBSD.ORG Fri Apr 3 03:21:53 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30904415 for ; Fri, 3 Apr 2015 03:21:53 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1DC2A810 for ; Fri, 3 Apr 2015 03:21:52 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id CE288341F948 for ; Thu, 2 Apr 2015 20:21:51 -0700 (PDT) Message-ID: <551E074E.5090803@mu.org> Date: Thu, 02 Apr 2015 20:21:50 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Bazaaring the cathedral (Lowering the Barrier to Entry) References: <201504021353.t32DrKd1075099@fire.js.berklix.net> In-Reply-To: <201504021353.t32DrKd1075099@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 03 Apr 2015 03:21:53 -0000 On 4/2/15 6:53 AM, Julian H. Stacey wrote: > Hans Petter Selasky wrote: >> I hope this is not one more of those April fools :-) > I've been thinking that since Eitan's first post of > Wed, 1 Apr 2015 09:55:11 -0700 (18:55 CEST) > "self-serve commit access" > I kept wondering what would keep looneys out ? :-) > > Your experience feeding back to Linux was interesting, I suppose > we assume "the grass is greener" till we hear someone tried it :-) > Agreed. Contributing to the git project itself was quite eye opening. They are very particular about the patch format and a few processes involved were very long. They also don't use github. That said, the community was pretty open to the patches (once I got the format correct) and it took about average amount of work to get my code submitted. -Alfred