From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 08:21:02 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C52996D for ; Sat, 25 Jan 2014 08:21:02 +0000 (UTC) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2DF7B1AB9 for ; Sat, 25 Jan 2014 08:21:02 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id up15so4098337pbc.36 for ; Sat, 25 Jan 2014 00:21:01 -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 :content-type; bh=YlYuzs0Btz3HvK21tzGn+SwDA7vuz4MhdWUEoifofp4=; b=cO+8ulEGiadI1ybOh8Gj08XOOki9/AM0s6yYUWXd09LBKazTUSopGzlUE7mboAfpMN L0QF5K8fAi3bb6I+0yQj1rV+IXpQjdVD7Evf0UDVFmvm9UK+/daK965DdziwoLSdPncv EPUovTH7HwrR32rf6lILxX/i76/HxmtGrNZDUgGqz1YU7+OWmzzXIqFpZzOnxoIN24KM X5lA0/x6N9sA2cthHCyByhrcCo9C9i+aspSUEcjiEPc5He/LRBE9B0xGSBOu+OprKOtC 1hbEzDMhNCg9nn/jqapWwsjFZ3gP4A4ueGdF610Q8wPoNbSlmXqC2P07tW5atVOjEYZt cQ4A== MIME-Version: 1.0 X-Received: by 10.68.247.6 with SMTP id ya6mr18668117pbc.45.1390638061764; Sat, 25 Jan 2014 00:21:01 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 25 Jan 2014 00:21:01 -0800 (PST) In-Reply-To: References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> <52E3719B.3040503@rawbw.com> Date: Sat, 25 Jan 2014 03:21:01 -0500 Message-ID: Subject: Fwd: What is the problem with ports PR reaction delays? From: Aryeh Friedman To: FreeBSD Ports ML , Yuri Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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 08:21:02 -0000 On Sat, Jan 25, 2014 at 3: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 makes >> this all as easy github, but I somehow doubt that.) >> > > github itself is closed source, but 95% of its functionality is based on > git which is open. One only needs to invoke 3-4 git operations to support > what it does on the website side. Register on the site, fork the project > under user's login, submit a pull request, merge a fork's branch to the > main branch. All these are basically git commands. Without the glossiness > of github, this is not that large of a project. Submitters will do the rest > through git. > > I think, instead of tediously going through the PRs by hand, it is wiser > to set up some system like this. This creates a "n+1" problem (something that jails are not advanced enough to completely solve but cloud computing can).... just for definitional shake a n+1 problem is based on the observation for all computer professionals (and hobbyists) always need at least one more "machine" then they currently have (this plus some techincal issues with OpenStack [Grizzly don't know if Havana fixes them]) is/was the primary motivator behind petitecloud in the first place... to that end any such system would need to set up and tare down VM's quickly as well keep a large number of them off line but for ready running... as far as testing goes the general method suggested in the paper I gave and eleberated in the Aegis user guide is a good starting place (it is especially good about making sure bugs stay fixed). -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org