From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: About that CommitFest redirect page ... |
Date: | 2008-09-06 22:34:56 |
Message-ID: | 20080906223456.GD4051@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-06 22:38:45 | Re: reducing statistics write overhead |
Previous Message | Tom Lane | 2008-09-06 22:32:52 | Re: [PATCH] "\ef <function>" in psql |