Subject: Re: Stalled news about ora2pg 11 on pg.org
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=iso-8859-1
From: "Jonathan S. Katz" <jonathan.katz@excoventures.com>
In-Reply-To: 
 <CABUevExzutQiWf++WqkUgh5Jr9+JU2akf1L1FWvP+HGsWbbGeA@mail.gmail.com>
Date: Tue, 16 Apr 2013 10:10:46 -0400
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
	Bruce Momjian <bruce@momjian.us>, Josh Berkus <josh@agliodbs.com>,
	PostgreSQL WWW <pgsql-www@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6F1D47B-E68E-4134-AEBE-E050C5D2C89F@excoventures.com>
References: <516C4833.2050805@dalibo.info>
	<CA+U5nMKRFBp9vhO_+Y4XJpvd00HDn4P0UDyoNDZ77=Bq8fVypg@mail.gmail.com>
	<516C5A96.4020006@agliodbs.com> <20130415195918.GA4602@momjian.us>
	<CABUevEyaP10u6ZYrRb+VHt7LW6+wdiSFj+58HbczrUfhzPYBxA@mail.gmail.com>
	<20130415201046.GD8626@eldon.alvh.no-ip.org>
	<CABUevEyp4mUmyc=ZZ6E++DL-yGJ2oqi9binN=BnNCiqva7rBhw@mail.gmail.com>
	<B6B1FF55-055B-41AF-BE4A-B78A99D11A59@excoventures.com>
	<CABUevExzutQiWf++WqkUgh5Jr9+JU2akf1L1FWvP+HGsWbbGeA@mail.gmail.com>
To: Magnus Hagander <magnus@hagander.net>
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Apr 16, 2013, at 3:10 AM, Magnus Hagander wrote:

> On Tue, Apr 16, 2013 at 12:58 AM, Jonathan S. Katz
> <jonathan.katz@excoventures.com> wrote:
>> On Apr 15, 2013, at 4:19 PM, Magnus Hagander wrote:
>>=20
>>> On Mon, Apr 15, 2013 at 10:10 PM, Alvaro Herrera
>>> <alvherre@2ndquadrant.com> wrote:
>>>> Magnus Hagander wrote:
>>>>> On Mon, Apr 15, 2013 at 9:59 PM, Bruce Momjian <bruce@momjian.us> wro=
te:
>>>>>> On Mon, Apr 15, 2013 at 12:52:54PM -0700, Josh Berkus wrote:
>>>>>>>=20
>>>>>>>> 2ndQuadrant has experienced significant delays in at least 3 cases
>>>>>>>> also. There is definitely a problem somewhere there.
>>>>>>>=20
>>>>>>> The delay is called "volunteer moderators who have day jobs".
>>>>>>>=20
>>>>>>>> Perhaps we should make all posts wait the same length of time, to
>>>>>>>> allow reasonable time to decide whether posts are suitable? 72 hou=
rs
>>>>>>>> seems like a reasonable time for this.
>>>>>>>=20
>>>>>>> Who is going to do this strictly time-limited approving?
>>>>>>=20
>>>>>> So it auto-approves after 72 hours?  I found this proposal vague.
>>>>>=20
>>>>> If anything automatic were to happen after 72 hours, the reasonable
>>>>> thing would be a rejection.
>>>>=20
>>>> ... but that's not more helpful than not doing anything, because then
>>>> the submitter needs to submit again.  This creates a busy loop on which
>>>> submitter needs to watch status of his submitted news until it gets
>>>> approved.
>>>=20
>>> I agree. But it's the only thing we could do at all there.
>>>=20
>>>=20
>>>> I think the idea behind 72-hour auto-approve is that if it's obvious
>>>> spam someone will quickly reject it, and if it's not spam then it's not
>>>> worth rejecting.  I don't think this is very palatable either.
>>>=20
>>> Given thta our moderators *clearly* don't have time to process it,
>>> this is almost *guarantee* to get spam postings onto our site. It
>>> won't work.
>>>=20
>>> I think recruiting more moderators, or somehow convincing our current
>>> ones to actually moderate more often is the only way to go.
>>=20
>> If helping to alleviate some of the delay issues would be to have more m=
oderators, I would be happy to volunteer my time.
>=20
> We can certainly do with more moderators. Unless there are any
> objections, I think adding Jonathan would be a good idea?
>=20
>> Perhaps another initiative (though this is a tech suggestion) is to send=
 a daily digest of news stories awaiting approval to the moderators so that=
 way there is a constant reminder to review news items.
>=20
> This is something we already do, since many years back.

Well, I think with that in place + a diligent moderation effort, that shoul=
d prevent backlogs.

Jonathan

--=20
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www