From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 17:30:53 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62966DC3; Sat, 25 Jan 2014 17:30:53 +0000 (UTC) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 293BE12A3; Sat, 25 Jan 2014 17:30:53 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id v10so4278242pde.28 for ; Sat, 25 Jan 2014 09:30:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KRl6p49JjwGn4kRbj+i89QEQskmwtj1V7x8jdkeuVZY=; b=R51geQKzp0Ytmq6slhc/3rblPL+ILlo1YfBqUReCpq0PjQRIuwomCQRWHhFERsvy6Q kKCuIG0gXJ5qglABLL352+TFR38GqeeJapG9FBHkcuwKXfrTs+1135v+pJ1x3i8kr96n IwO/JLfS5UqzKJc5VH1gTmazusbqCxX5cAOaCdmGyYQOenb8+w+Uk4VxyLwtdULkT6Nt +k1gzC/gfqLdwhmAMIDWad3S80WUf/8hiN4IrpWIfkNfwLCKq9aVH+czCkskCn4wqwvo vsz1QxzkD5hkJyz9m1nrRZlHmUyS7KJfaDown7DYvAlZCk9PnuMVgtAxDP+GpZz3Z3sW XazQ== MIME-Version: 1.0 X-Received: by 10.66.179.143 with SMTP id dg15mr21134979pac.52.1390671052789; Sat, 25 Jan 2014 09:30:52 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 25 Jan 2014 09:30:52 -0800 (PST) In-Reply-To: <52E3F03C.1060503@freebsd.org> References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> <52E36BA1.5030900@marino.st> <52E37C16.5080901@freebsd.org> <52E3806D.4020902@marino.st> <52E3F03C.1060503@freebsd.org> Date: Sat, 25 Jan 2014 12:30:52 -0500 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Aryeh Friedman To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: John Marino , marino@freebsd.org, FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 17:30:53 -0000 > By the way, this wasn't about switching to git (although that would be > nice), this is about leveraging existing tools. > > One can very easily use git-svn bridge to push git changes into > subversion. Or you can try to re-implement a patch queue based system > yourself using a bunch of duct tape and bailing wire and likely get > frustrated and either never complete it OR complete it and it's just not > even half as good as git as a patch manager. > > Use the existing tools. > > I implore you to explore the idea of using existing tools to solve the > problem, or at least solve a part of the problem, instead of trying to > reinvent functionality that already exists devel/tailor (which I maintain but never used) is designed to automatic convert repos from one scm to an other this might be the best solution... also I think the devel/aegis model of develop-->test-->review-->integrate (which is built in by default but can be turned of or configured) might help here (no need for changing tools unless we want to since most of this is procedural) the basic model is: 1. One person develops 2. An other reviews 3. Yet an other intergates I think the first 2 is what we need to focus on. Namely when a new port comes it is assigned a perm reviewer/integrator (aka comitter) and all changes to that port from hence forth have that person as the assigned comitter -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org