Re: News moderation

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: News moderation
Date: 2009-06-09 18:26:35
Message-ID: 937d27e10906091126j4f1135d6hb6352844adb3ee38@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Tue, Jun 9, 2009 at 6:06 PM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
> Dave,
>
>> Huh? It's not exactly hard now. Open the item, check it, click the
>> approved checkbox and hit submit/save. It's not likely to get any
>> easier, without removing the need to open it - and you can't properly
>> moderate anything you didn't write yourself without opening it and
>> reading it anyway.
>
> Examples:
>
> 1) We have a policy that non-contributing companies only get one News every
> 6 months, period.  Try to search on how many announcements a company has had
> in 6 months.
>
> 2) We have a policy of no minor releases or betas, *unless* it's the first
> PG support by the product.  Try to search on whether a particular product
> has ever been announced before.
>
> 3) Try to figure out how many training events a specific company is
> submitting.  Or whether they've submitted duplicate listings *without*
> approving and of the events first.
>
> 4) If we want to reject an item with feedback, there is no "reject with
> feedback" button, let alone canned standard responses.
>
> 5) There is no way to flag an item as "please do not approve, awaiting
> response from submitter" so that we can "hold" stuff while we check
> something.  Or while we discuss stuff on -slaves.
>
> 6) The professional services form does not have any required fields, meaning
> that we have to bounce about 50% of submissions on not having enough
> information.
>
> We can work around all of the above, but it's labor-intensive.  Which is one
> reason why you see people dropping behind on approvals, or simply approving
> everything whether it's in our policy or not.

None of which would have been fixed in any new backend, as noone has
previously reported these issues as far as I'm aware. If people are
quitting moderating for actual technical reasons, telling us would be
most helpful. Most people will report bugs and inconveniences in
PostgreSQL quite happily, so it's a mystery why they wouldn't report
issues with processes when help run the project.

I can't honestly say any of them have caused me any real pain though.
All valid points I grant you, but minor inconveniences in my
experience.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Josh Berkus 2009-06-09 18:33:57 Re: News moderation
Previous Message Josh Berkus 2009-06-09 17:06:20 Re: News moderation