Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U3qlC-00009L-Bg for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Feb 2013 16:25:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U3qlA-0001YQ-Ow for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Feb 2013 16:25:08 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U3qky-0001P3-C7 for pgsql-hackers@postgresql.org; Fri, 08 Feb 2013 16:24:56 +0000 Received: from zql.com ([206.222.31.58]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U3qkx-0003eW-1T for pgsql-hackers@postgresql.org; Fri, 08 Feb 2013 16:24:55 +0000 Received: from localhost.localdomain ([127.0.0.1] helo=localhost) by zql.com with smtp (Exim 4.68) (envelope-from ) id 1U3qkv-00060l-LF; Fri, 08 Feb 2013 11:24:53 -0500 From: "Greg Sabino Mullane" To: pgsql-hackers@postgresql.org Subject: Re: Considering Gerrit for CFs X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 In-Reply-To: <511517C7.6070306@gmx.net> Date: Fri, 8 Feb 2013 16:24:53 -0000 X-Mailer: JoyMail 2.4.0 Message-ID: X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > How would this go with PostgreSQL? You can use the bug form on the web > site, but you can't attach any code, so the bug will just linger and > ultimately put more burden on a core contributor to deal with the > minutiae of developing, testing, and committing a trivial fix and > sending feedback to the submitter. Well, they could attach a link to a github patch... > Or the user could take the high road and develop and patch and submit it. > Just make sure it's in context diff format! Search the wiki if you don't > know how to do that! Send it to -hackers, your email will be held for > moderation. We won't actually do anything with your patch, but we will > tell you to add it to that commitfest app over there. You need to sign up > for an account to use that. We will deal with your patch in one or two months. > But only if you review another patch. And you should sign up for that > other mailing list, to make sure you're doing it right. Chances are, the > first review you're going to get is that your patch doesn't apply anymore, > but which time you will have lost interest in the patch anyway. +1 to all that. Especially the signing up for the commitfest app. > Of course, Gerrit doesn't actually address most of the issues above, but > it could be part of a step forward. More of a step sideways. It doesn't address the bigger problems. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 201302081124 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlEVJrkACgkQvJuQZxSWSshh3gCgz+XHwAbk5rryttYPi68j4EJi 7DcAnjEdxDD4Rm2/oDBaqHbOzQLwR6zR =0lnp -----END PGP SIGNATURE----- 2~ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers