Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URsLt-0006mj-U5 for pgsql-www@arkaria.postgresql.org; Mon, 15 Apr 2013 22:58:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1URsLs-0005rU-Ql for pgsql-www@arkaria.postgresql.org; Mon, 15 Apr 2013 22:58:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URsLs-0005rO-2H for pgsql-www@postgresql.org; Mon, 15 Apr 2013 22:58:20 +0000 Received: from mail-vc0-f172.google.com ([209.85.220.172]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URsLn-0005j3-QW for pgsql-www@postgresql.org; Mon, 15 Apr 2013 22:58:19 +0000 Received: by mail-vc0-f172.google.com with SMTP id gd11so4471347vcb.3 for ; Mon, 15 Apr 2013 15:58:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=MUFVbXqKZVyj/IGyYSnD5P29hW6w46mGIWDnYKPVZ90=; b=pZeFecCrWareo6+gY1ZtV+XAqxB3WpD1WxE0yGBuyT2Yz/hIgSqLOVtUoWrzU6PQmu qS5UDuKM2xvicYBtIbzfEzlrBFipHppQ2qJzJSLeQ349Yy6Vg2+lV3s6yOkMLizRElhO 9AS1C4CKqajQQrQkzDJE4X8aleC0SjskgV3T26irNfSpK+LdePx7zcbGMln+3kAF/hdw R9n0cH/PmEYPZv20HK6oewf48h4fCOsotivKXnYiJUH+8oXluuZThNPpVUaf0OfTyRmh IzRmCETyCR4uBNlov1bNEyahQEOKY+9+P4fFvrzTZIq8LnmSqryPvhxA3ekO/QHsf3S7 kt1Q== X-Received: by 10.58.212.8 with SMTP id ng8mr17664142vec.25.1366066694765; Mon, 15 Apr 2013 15:58:14 -0700 (PDT) Received: from ph33r-retina.home (pool-108-41-19-41.nycmny.fios.verizon.net. [108.41.19.41]) by mx.google.com with ESMTPS id b9sm21264455vee.3.2013.04.15.15.58.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Apr 2013 15:58:13 -0700 (PDT) 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" In-Reply-To: Date: Mon, 15 Apr 2013 18:58:10 -0400 Cc: Alvaro Herrera , Bruce Momjian , Josh Berkus , PostgreSQL WWW Content-Transfer-Encoding: quoted-printable Message-Id: References: <516C4833.2050805@dalibo.info> <516C5A96.4020006@agliodbs.com> <20130415195918.GA4602@momjian.us> <20130415201046.GD8626@eldon.alvh.no-ip.org> To: Magnus Hagander X-Mailer: Apple Mail (2.1280) X-Gm-Message-State: ALoCoQlk+0jmJOnNANBBUwZJpdJ65DweShXZoeU5VHAY3qMAaIPCmInAGPNqXjMdz5KbQ7YBylVd X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org On Apr 15, 2013, at 4:19 PM, Magnus Hagander wrote: > On Mon, Apr 15, 2013 at 10:10 PM, Alvaro Herrera > wrote: >> Magnus Hagander wrote: >>> On Mon, Apr 15, 2013 at 9:59 PM, Bruce Momjian wrote: >>>> 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 hours >>>>>> 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. If helping to alleviate some of the delay issues would be to have more mode= rators, I would be happy to volunteer my time. 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 wa= y there is a constant reminder to review news items. 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