From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 2 09:33:24 2015 Return-Path: Delivered-To: freebsd-hackers@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 6B6C61B2; Thu, 2 Apr 2015 09:33:24 +0000 (UTC) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D47355EF; Thu, 2 Apr 2015 09:33:23 +0000 (UTC) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.14.9/8.14.9) with ESMTP id t329XJwg013591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Apr 2015 09:33:19 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.14.9/8.14.9/Submit) with ESMTP id t329XIVQ013578; Thu, 2 Apr 2015 09:33:19 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Thu, 2 Apr 2015 09:33:18 +0000 From: Marcin Cieslak To: Eitan Adler Subject: Re: Bazaaring the cathedral (Lowering the Barrier to Entry) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Hackers , freebsd-current Current X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 09:33:24 -0000 On Wed, 1 Apr 2015, Eitan Adler wrote: > Hi all, > > One of the key reasons for the lack of people is the high barrier of > entry to joining the FreeBSD project. While every modern project uses > git (usually hosted on github), As much as I love github - please try to go to http://github.com/freebsd/freebsd-ports and try to view history of one particular port. Example task I am facing right now: "I need to compile iojs 1.0.4 using older version of FreeBSD port". Github web interface says to me: > > Sorry, this commit history is taking too long to generate. > > Refresh the page to try again, or view this history locally using the following command: > > git log master -- www/iojs/Makefile Sure one might argue every ports should be a separate repository and we should use git submodules. No, thank you. > Our wiki and code review tools are in an even worse position than our > repository. In order to contribute you need to send an email to > clusteradm@ and hope they deem you worthy enough of access. The bug > tracking system is in a better shape but isn't perfect: while any user > can create an account, their privileges are limited: they can't help > close out bad PRs, reclassify good ones, or do other generally useful > work. I am pretty frustrated I can't login to Phabricator without @freebsd.org address. This is something that should be addressed _ReallySoonNow_ I don't follow FreeBSD intrastructure discussions but I don't understand while we jumed from gnats onto bugzilla instead of going straight to Phabricator Maniphest. Also from my Phabricator experience it is still a bit better suited for svn-centralized model than git (although it supports git as well). > Today I hope we turn ourselves from the cathedral into a truly open > and democratic project! I'd love to have a Phabricator account but despite using FreeBSD since I think version 2.1 and contributing very little I never aspired to get a commit bit. //Marcin