Message-ID: <47CDB22F.40308@hagander.net>
Date: Tue, 04 Mar 2008 21:33:51 +0100
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: "Joshua D. Drake" <jd@commandprompt.com>
CC: Selena Deckelmann <selenamarie@gmail.com>, pgsql-www@postgresql.org
Subject: Re: Technical Mailing list creation policy
References: <20080304091501.54777bd8@commandprompt.com>
	<2b5e566d0803041200nb94b0e8ua1ea85dc8b7166f2@mail.gmail.com>
	<20080304120228.7eeda208@commandprompt.com>
In-Reply-To: <20080304120228.7eeda208@commandprompt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Joshua D. Drake wrote:
> On Tue, 4 Mar 2008 12:00:03 -0800
> "Selena Deckelmann" <selenamarie@gmail.com> wrote:
> 
>>>  I think we need to put in place a technical policy that says that
>>> the mailing list creation is the last step of the process. E.g;
>>>
>>>  1. Patch archives
>>>  2. Patch community/lists
>>>  3. create mailing list
>> Also patch:
> 
>> 4. http://www.postgresql.org/community/lists/subscribe
> 
> 
> +1
> 
> I would note that yes this should all be databased and I can look at it
> (as yet another item on the list) but until that time, we need to
> enforce something.

I'm working on code for this and has most of it done :-) Now to find 
that time to test it so it doesn't kill everything :-)

That will take care of all the stuff that's on www.postgresql.org and 
also search.postgresql.org (which is missing from the bullet list 
above). Eventually, it will also take care of archives (in step 2, but I 
haven't looked at code for that yet)

//Magnus