Date: Sat, 25 Jan 2014 12:30:52 -0500 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: Alfred Perlstein <alfred@freebsd.org> Cc: John Marino <dragonflybsd@marino.st>, marino@freebsd.org, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <CAGBxaXmXnt0ghBSh0V%2BFU1xTmGtH8dB4ZNcHZBE3he%2Bca%2Bh7jg@mail.gmail.com> In-Reply-To: <52E3F03C.1060503@freebsd.org> References: <CAHcXP%2Bf6e-t--XbQPTH1goJp_CL7P=zTj5trZVWd4YZ_EsO9gw@mail.gmail.com> <52E2FA36.5080106@marino.st> <CAHcXP%2BfRDeKXjz0_sifgzeXC2dA-eDnoV5NH1yvF2D6R8JRmAg@mail.gmail.com> <52E303CB.6020304@marino.st> <CAHcXP%2Be9p2HrQ=M9HmPecMbWtXRuYPzH9kwfLGqgdrUrhvLuEA@mail.gmail.com> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> <52E36BA1.5030900@marino.st> <52E37C16.5080901@freebsd.org> <52E3806D.4020902@marino.st> <52E3F03C.1060503@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGBxaXmXnt0ghBSh0V%2BFU1xTmGtH8dB4ZNcHZBE3he%2Bca%2Bh7jg>