Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 11CA02E30BD
	for <pgsql-hackers-postgresql.org@postgresql.org>;
	Sat,  8 Mar 2008 03:50:41 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 03523-07 for
	<pgsql-hackers-postgresql.org@postgresql.org>;
	Sat,  8 Mar 2008 03:50:38 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
	by postgresql.org (Postfix) with ESMTP id 7FB3B2E01A0
	for <pgsql-hackers@postgresql.org>;
	Sat,  8 Mar 2008 03:50:38 -0400 (AST)
Received: by fg-out-1718.google.com with SMTP id 22so682988fge.23
	for <pgsql-hackers@postgresql.org>;
	Fri, 07 Mar 2008 23:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=ZP8PE/MY2HavL9197Xt4Dda8JVLBP+hhQDBK5ySeIzY=;
	b=BzNt1rGyR7lxtneCCN/Mgzf4BczhaCP3MI62SoZtqfLUzyKaZxocbbOZzrMzOGVGeSqIaKi7ZPDTPo2lzf4OiCBd13waXnqkbllNVipU98cBg0cl0JwzNlCGvyZzeQElQuqTDJPMnlVTsTVWcLGwVum5uzpxUTVhgydrC0NAk2M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=R04B5El9JiKaohUk8UlWy1szkb7IMLzGFVcnVTcJmyWbCuJU/ssNP/shr6J5qpJac373MX+/TLduaqLjvBeojTw2f78+vJgQ29selmFC2Pr+AMYZnUE43IAzdSZGxALz/o0dNKcuhUZ9LakWyBMsqXgI+ZX24tRw+LEKhbcN3Ng=
Received: by 10.86.51.2 with SMTP id y2mr2778031fgy.15.1204962637499;
	Fri, 07 Mar 2008 23:50:37 -0800 (PST)
Received: by 10.86.30.14 with HTTP; Fri, 7 Mar 2008 23:50:37 -0800 (PST)
Message-ID: <37ed240d0803072350m521c2bcay6743b0269439eef1@mail.gmail.com>
Date: Sat, 8 Mar 2008 18:50:37 +1100
From: "Brendan Jurd" <direvus@gmail.com>
To: "Heikki Linnakangas" <heikki@enterprisedb.com>
Subject: Re: Commitfest process
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <47D18D80.2050107@enterprisedb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47D1521E.8090606@enterprisedb.com>
	<20080307101413.7d191e52@commandprompt.com>
	<47D18D80.2050107@enterprisedb.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200803/214
X-Sequence-Number: 115015

On 08/03/2008, Heikki Linnakangas <heikki@enterprisedb.com> wrote:
>  I think we'll have more success convincing patch authors to update a
>  wiki page, than we'll have to convince reviewers to do so. I know that's
>  true at least for me. If I want people to review my patch, I'm ready to
>  sing and dance if that's what it takes. But if there's extra steps in
>  reviewing a patch, I might just not bother.

+1.  As a patch author, I have much more personal investment in a
patch than anyone else, and I'm happy to maintain a wiki page if it's
going to get my patches through the process more efficiently.

But I also agree with Josh Drake's comment about a single point of
entry.  If patch authors are updating the wiki, and reviewers are
using the wiki to guide their efforts, what purpose does the -patches
mailing list serve?  Does sending an email to -patches on top of
submitting the patch on the wiki actually buy us anything?  It seems
redundant.

Regards,
BJ