Message-ID: <470A796F.8000008@kaltenbrunner.cc>
Date: Mon, 08 Oct 2007 20:39:43 +0200
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
User-Agent: Icedove 1.5.0.12 (X11/20070607)
MIME-Version: 1.0
To: Josh Berkus <josh@agliodbs.com>
CC: pgsql-www@postgresql.org
Subject: Re: Approval process for news/events/training is broken
References: <470A72CD.4050304@agliodbs.com>
In-Reply-To: <470A72CD.4050304@agliodbs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Josh Berkus wrote:
> WWW folks,
> 
> I've just noticed again today that the way we approve news, events, and
> training for the front page is seriously broken.  Currently, if only
> *one* person with approval rights thinks that something is OK, it gets
> approved immediately.
> 
> This means that screw-ups like this morning happen repeatedly.  Namely,
> EDB posted a link-only announcement, which we've discussed before as not
> being acceptable for PostgreSQL.  I pinged Robert and asked him not to
> approve it, and phoned EDB's PR agent, and she was giving me new content
> ... when someone else decided to approve it.

well that particular news item was like 10 days old as far as I can see ...

> 
> We need the news/events system to change in two ways:
> 
> 1) There needs to be a way for admins to flag an item as "don't approve,
> there's a problem" so that if one person knows of a reason to hold,
> someone coming online later won't approve due to being clueless.

that seems doable though

> 
> 2) approvers should wait at least a couple of hours before approving
> things.

well ... see above


> 
> 3) We need a written policy of what is acceptable for
> news/events/training and what isn't.

sounds like a good thing - maybe simply have it as some sort of
checklist in the interface to check against ?


Stefan