Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1US025-0002Kg-LT for pgsql-www@arkaria.postgresql.org; Tue, 16 Apr 2013 07:10:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1US024-0001Cf-Tn for pgsql-www@arkaria.postgresql.org; Tue, 16 Apr 2013 07:10:24 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1US024-0001Ca-EL for pgsql-www@postgresql.org; Tue, 16 Apr 2013 07:10:24 +0000 Received: from mail-we0-x22c.google.com ([2a00:1450:400c:c03::22c]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1US021-0003Rx-FW for pgsql-www@postgresql.org; Tue, 16 Apr 2013 07:10:23 +0000 Received: by mail-we0-f172.google.com with SMTP id r3so108936wey.31 for ; Tue, 16 Apr 2013 00:10:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=H2hemE0+gDO2Ew3kSsohTWLdpROyxeJpq3gMJ9us9ow=; b=JMLYtCLyoKRBv3InGRQ+CuPEyw2+bNcfXGAxre45QhK6ktUWyeVBiven8jpMcqC9HN WVlEMP+GWk+ox0i/o6lzeiESS1nLU/Y8pvxJUZ/aayOFQ+xErdcv4n4lpnb7GDHL9c/L lbJyY5M9zaDJaKCyKU44YLbyazTWcWTcOQxb+XQA1iIhSpNCCl5Id5/OrqmihaipK3kl 8eXdc7VVyJAFcZkif/GwP1gAZPm/lmmAUORcdP1HkTBco36i4jqdaFZWXhWLpTklHrH8 xDqsx0WkFJzts3FCz9T1qTOCLJpfM0UHvK5MrUsPQnnWNMSwU7f7Qg4oG4kGT0GMLY/n b9Lg== MIME-Version: 1.0 X-Received: by 10.194.133.198 with SMTP id pe6mr1478627wjb.9.1366096218668; Tue, 16 Apr 2013 00:10:18 -0700 (PDT) Received: by 10.194.16.69 with HTTP; Tue, 16 Apr 2013 00:10:18 -0700 (PDT) In-Reply-To: References: <516C4833.2050805@dalibo.info> <516C5A96.4020006@agliodbs.com> <20130415195918.GA4602@momjian.us> <20130415201046.GD8626@eldon.alvh.no-ip.org> Date: Tue, 16 Apr 2013 09:10:18 +0200 Message-ID: Subject: Re: Stalled news about ora2pg 11 on pg.org From: Magnus Hagander To: "Jonathan S. Katz" Cc: Alvaro Herrera , Bruce Momjian , Josh Berkus , PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkFY2yHfOt216B2HrkJEYiEJ9YFPZXbcMva7KpasgPjd3qPHLfG/IgCoz8BUUnkpXkCGldY X-Pg-Spam-Score: -1.9 (-) 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 Tue, Apr 16, 2013 at 12:58 AM, Jonathan S. Katz wrote: > 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: >>>>>> >>>>>>> 2ndQuadrant has experienced significant delays in at least 3 cases >>>>>>> also. There is definitely a problem somewhere there. >>>>>> >>>>>> The delay is called "volunteer moderators who have day jobs". >>>>>> >>>>>>> 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. >>>>>> >>>>>> Who is going to do this strictly time-limited approving? >>>>> >>>>> So it auto-approves after 72 hours? I found this proposal vague. >>>> >>>> If anything automatic were to happen after 72 hours, the reasonable >>>> thing would be a rejection. >>> >>> ... 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. >> >> I agree. But it's the only thing we could do at all there. >> >> >>> 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. >> >> 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. >> >> 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 moderators, I would be happy to volunteer my time. We can certainly do with more moderators. Unless there are any objections, I think adding Jonathan would be a good idea? > 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. This is something we already do, since many years back. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www