public inbox for [email protected]
help / color / mirror / Atom feedFrom: Stefan Kaltenbrunner <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Approval process for news/events/training is broken
Date: Mon, 08 Oct 2007 20:39:43 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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
view thread (31+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Approval process for news/events/training is broken
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox