public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: Pg Hackers <[email protected]>
Subject: Re: Patch queue -> wiki (was varadic patch)
Date: Wed, 02 Apr 2008 15:43:48 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>



Tom Lane wrote:
>
> For the past couple of weeks I've been dealing with both Bruce's queue
> and the one at
> http://wiki.postgresql.org/wiki/CommitFest:March
> and frankly I find the latter a *whole* lot more satisfactory, despite
> the fact that it's got exactly zero custom tooling or infrastructure
> behind it.  It doesn't have artificial constraints on page organization;
> I can update it as soon as I've done something rather than waiting
> around for Bruce to do so; and there's an automatically maintained
> history of changes.  Bruce has put a whole lot of man-hours into
> getting his page to do a few of the things we could do for free with
> the wiki page, but it's still got a long way to go.
>
> Now it would certainly be nice if there were some tools that would
> assist with dumping URLs for newly-arrived messages into the wiki page.
> Perhaps some of the pgsql-www crowd can think about how to do that.
> But even if we had to do that entirely by hand, I'd rather go with the
> wiki page.
>
> At some point it might be worth building the sort of heavy-duty
> infrastructure for the patch queue that you have in mind here.
> I don't think we need it yet, though, and I definitely don't think
> we understand our requirements well enough yet to start designing
> it.  One of the reasons I like the wiki approach is exactly that
> there's such a low barrier to getting started with it.
>
> 			
>   

+ MAXINT.

cheers

andrew

view thread (57+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Patch queue -> wiki (was varadic patch)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox