Date: Sat, 25 Jan 2014 00:11:07 -0800 From: Yuri <yuri@rawbw.com> To: freebsd-ports@FreeBSD.org Cc: Alfred Perlstein <alfred@FreeBSD.org> Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <52E3719B.3040503@rawbw.com> In-Reply-To: <52E33AA7.3080205@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E3719B.3040503>