Skip site navigation (1) Skip section navigation (2)

Re: Patch queue -> wiki (was varadic patch)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch queue -> wiki (was varadic patch)
Date: 2008-04-02 23:35:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-www
Tom Lane wrote:
> For the past couple of weeks I've been dealing with both Bruce's queue
> and the one at
> 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.

It is not clear to me how a wiki can be easily created for 2k emails and
then maintained in a reasonable way, or how emails can be added to it

There are several steps:

	o  getting those 2k emails to start the commit fest
	o  getting them into a wiki in a way that is fast/efficient
	o  updating the wiki for changes efficiently

Keep in mind the patch emails are pretty dynamic.  As you get closer to
the end of the commit fest, the wiki is easier because the list of open
items becomes more stable.

I am able to give others the ability to add, move, and delete emails in
my patch queue, if desired.

If people want to use the wiki, go ahead --- this would be one less job
for me to do.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-www by date

Next:From: Joshua D. DrakeDate: 2008-04-02 23:38:00
Subject: Re: Advertizing email footers
Previous:From: Josh BerkusDate: 2008-04-02 23:33:06
Subject: Re: Advertizing email footers

pgsql-hackers by date

Next:From: Ron MayerDate: 2008-04-02 23:41:16
Subject: modules
Previous:From: Marc G. FournierDate: 2008-04-02 23:18:03
Subject: Re: Several tags around PostgreSQL 7.1 broken

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group