Re: About that CommitFest redirect page ... - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: About that CommitFest redirect page ...
Date
Msg-id 20080906223456.GD4051@alvh.no-ip.org
Whole thread Raw
In response to About that CommitFest redirect page ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: About that CommitFest redirect page ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> So according to
> http://wiki.postgresql.org/index.php?title=CommitFest&action=history
> there's been rather a lot of confusion about where the CommitFest
> redirect page should point when.
> 
> I think the problem is that we need two redirect pages: one for "the
> place where you should submit a new patch" and one for "the commitfest in
> progress".  The problem is to choose names that will make it reasonably
> obvious which is which.

I suggest two redirects CommitFestInProgress and CommitFestOpen, and
turning CommitFest into a plain page with suitable text pointing to both
redirects.

We'd also need a page saying "there is no commitfest currently in
progress; maybe you wanted to go to CommitFestOpen instead?" to point
the CommitFestInProgress to in the period between commitfests.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] "\ef " in psql
Next
From: Tom Lane
Date:
Subject: Re: reducing statistics write overhead