Date: Sat, 25 Jan 2014 03:21:01 -0500 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: FreeBSD Ports ML <freebsd-ports@freebsd.org>, Yuri <yuri@rawbw.com> Subject: Fwd: What is the problem with ports PR reaction delays? Message-ID: <CAGBxaXnrZ4AL8Z1vj%2BMQjhwkdWktXUdLQzStE%2BbcqOLN4AEAyw@mail.gmail.com> In-Reply-To: <CAGBxaX=wzKzgogHHbm3ZwmpMZe407tzgsHYNu5L1_tbrF8BcQA@mail.gmail.com> 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> <52E3719B.3040503@rawbw.com> <CAGBxaX=wzKzgogHHbm3ZwmpMZe407tzgsHYNu5L1_tbrF8BcQA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 25, 2014 at 3:11 AM, Yuri <yuri@rawbw.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGBxaXnrZ4AL8Z1vj%2BMQjhwkdWktXUdLQzStE%2BbcqOLN4AEAyw>