From owner-freebsd-ports@freebsd.org Wed Dec 16 13:14:28 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB4EFA48D5F for ; Wed, 16 Dec 2015 13:14:28 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6EEE33C37; Wed, 16 Dec 2015 13:14:28 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id tBG9qcO3030689 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 16 Dec 2015 01:52:39 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com Subject: Re: Gogs port: A painless self-hosted Git service To: =?UTF-8?Q?Torsten_Z=c3=bchlsdorff?= , Matthew Seaman , freebsd-ports@freebsd.org References: <566D38ED.7050406@rawbw.com> <566D5B3C.4040602@FreeBSD.org> <566E75C3.9090601@toco-domains.de> From: Yuri Message-ID: <56713466.9090609@rawbw.com> Date: Wed, 16 Dec 2015 01:52:38 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <566E75C3.9090601@toco-domains.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2015 13:14:28 -0000 On 12/13/2015 23:54, Torsten Zühlsdorff wrote: > I did this often for different processes. I won't work on the issue > this year - there is do much open to do. > > But please write me a desired workflow and the needed requirements and > i will do this in the next year. Just 3 weeks to go :D This isn't a complete workflow, but here is an idea for port updates: Each port update or new port submission could become a pull request. Once the new pull request is created, system should launch poudriere builds for it for all required platforms, and append the notice that builds have started. Then append the build status. If it was successful, committer can just approve the change with one press of a button. I believe there is a way to do a two way sync between git and subversion. If at any point in time that port changes, the process has to be invalidated and restarted if the pull request is still mergeable, or submitter should be notified if it became unmergeable. This could simplify and expedite the process of committing of port changes. Yuri