Message-ID: <46B4BFB2.3090902@pooteeweet.org>
Date: Sat, 04 Aug 2007 20:04:34 +0200
From: Lukas Kahwe Smith <smith@pooteeweet.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Magnus Hagander <magnus@hagander.net>
CC: Dave Page <dpage@postgresql.org>,  pgsql-advocacy@postgresql.org
Subject: Re: [pgsql-www] We need an Advocacy wiki
References: <200708041813350000@3057932291> <46B4BD3A.2060301@pooteeweet.org>
	<46B4BEAE.4040308@hagander.net>
In-Reply-To: <46B4BEAE.4040308@hagander.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-backendmedia-com-MailScanner-Information: Please contact the ISP for more
	information
X-backendmedia-com-MailScanner: Found to be clean
X-backendmedia-com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
	score=0.097, required 6, AWL -0.00,
	RDNS_DYNAMIC 0.10)
X-backendmedia-com-MailScanner-From: smith@pooteeweet.org
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200708/67
X-Sequence-Number: 11637

Magnus Hagander wrote:
> Lukas Kahwe Smith wrote:
>> Dave Page wrote:
>>
>>> Using a wiki for a public website looks completely unprofessional and
>>> gives the impression of a small organisation without the resources to
>>> do things properly. 
>> Honestly I dont think that our target audience cares much. What I do
> 
> Apparently we define our target audience a lot differently ;-) What
> group does not notice an unprofessional web presence these days?

Well my idea if an average PostgreSQL user is not one who would be 
turned off by the idea of a wiki in general. I also do not think that a 
wiki is unprofessional by definition.

> That method leaves it very possible for incorrect data to be up on the
> main site for three months, which is IMHO unacceptable. I can accept
> that for a community collaboration site (like the current wiki), but not
> for the main web presence. "Moderation" has to happen before the fact
> there. (that's a principle completely unrelated to if a wiki is used or
> not - I assume there are wikis that can deal with that workflow as well)

Oh maybe I missed something here, but I did not realize that we are 
discussing replacing the main site with a wiki. I just think that the 
wiki is perfect when we want to involve a broad audience in the creation 
of the text (which may very well then we moved to techdoc or the 
documentation later on) or when its just for a quick one shot with a 
life time if a few weeks (months tops).

regards,
Lukas