From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 17:51:55 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 BE091AFA; Sat, 25 Jan 2014 17:51:55 +0000 (UTC) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A147146A; Sat, 25 Jan 2014 17:51:55 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id a1so4078921wgh.4 for ; Sat, 25 Jan 2014 09:51:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=/MaLg/oBC+m73IQ9055GK0/GngZFYbHhbIFlKxwloew=; b=h+E49L/DnIDCN5i/fNOCq8njeCDUyy3heL0WyHWxnKTGnP1G2eBzfYfftLCxbwISLk JiVLecO9IMR1USz0r182WDuAwjJo+If3sI40tsLHy41GkmPwrUDShvGoth+ihJaxPxZP cdjaZcrUDobxAlMR9jqdUjjzQfEGouDJwFtNrXkZNbPYjg/IGTju8m2InvJ89O3C+pFX hMr6yEt5PdmAMdjsy4S0HR99d45PcTV0eoO34PNYexMFEVGhSBYS+M536tDmKRYe3mGd MN/oKKd2WkCwpprwH8F7kU42RMCdQujJVUKI1Gw6qZfMeNu7Ovd42ZRcWjm68rNzik7+ CnMA== X-Received: by 10.194.75.198 with SMTP id e6mr14677588wjw.3.1390672313527; Sat, 25 Jan 2014 09:51:53 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id y13sm11344688wjr.8.2014.01.25.09.51.52 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 25 Jan 2014 09:51:52 -0800 (PST) Sender: Baptiste Daroussin Date: Sat, 25 Jan 2014 18:51:50 +0100 From: Baptiste Daroussin To: Alfred Perlstein Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <20140125175150.GB67191@ithaqua.etoilebsd.net> References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> <52E3719B.3040503@rawbw.com> <52E37C71.1060906@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: <52E37C71.1060906@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Yuri , freebsd-ports@FreeBSD.org 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:51:55 -0000 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 25, 2014 at 12:57:21AM -0800, Alfred Perlstein wrote: >=20 > On 1/25/14, 12:11 AM, Yuri wrote: > > On 01/24/2014 20:16, Alfred Perlstein wrote: > >> (maybe there is some great ports system that I'm not aware of that=20 > >> makes this all as easy github, but I somehow doubt that.) > > > > github itself is closed source, but 95% of its functionality is based= =20 > > on git which is open. One only needs to invoke 3-4 git operations to=20 > > support what it does on the website side. Register on the site, fork=20 > > the project under user's login, submit a pull request, merge a fork's= =20 > > branch to the main branch. All these are basically git commands.=20 > > Without the glossiness of github, this is not that large of a project.= =20 > > Submitters will do the rest through git. > > > > I think, instead of tediously going through the PRs by hand, it is=20 > > wiser to set up some system like this. > > > Agreed. +1000 >=20 > Although if we go down the rabbit hole of building something "like=20 > github" that might take a while. For now prototyping using the github=20 > pull methods might be a good proof of concept. I may look into doing a= =20 > github pull request -> GNATS (src) PR gateway if time allows. Once again github pull request is the worst way of merging patches that exi= sts. We already have problem with ugly and inaccurate logs, such pull request wi= ll make it even worse. Making proper merge from github pull request it not that easy, you will nee= d to fetch pull request as custom branches and cherry-pick them. That is really = not convenient. regards, Bapt --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iEYEARECAAYFAlLj+bYACgkQ8kTtMUmk6EygywCgqdbWFiNuGF/9PZIdNqjWbCf6 Z5AAn1sY07FTJiY4XicQfUVocEABKbns =SwxP -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY--