Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtPGz-0004G1-HA for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2013 21:02:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TtPGy-0003Xq-Tm for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2013 21:02:48 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtPGx-0003Wv-Um for pgsql-www@postgresql.org; Thu, 10 Jan 2013 21:02:48 +0000 Received: from mail-qc0-f173.google.com ([209.85.216.173]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtPGu-0007Hj-Vo for pgsql-www@postgresql.org; Thu, 10 Jan 2013 21:02:47 +0000 Received: by mail-qc0-f173.google.com with SMTP id b12so683406qca.32 for ; Thu, 10 Jan 2013 13:02:42 -0800 (PST) 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=xvWtk5ObqHFzIeKr3wXDsqxpgXmtglPp1wREVrtQquI=; b=YRJEVTFun4v0HgpvUTgE5EIWpg8N2crxr9iCTtCkbvyx8KiY740wg1qrhz1mtz8ZVl JNur6Vv87D1xhbcZ3KDJtgFbL/68sGOV2PgH8wq/qUwmQMoQzI3jbUr7hYThukkkmKEn jkFQYD0DbsfDbRWk3nf4pU74wV5nYCRSx6yP9JKV/gxsXjOZls12gVN9qFjA6bAqRAZo //gs40vzpkDJQTKfO9UiLzS7p7G7QsyIxx8rpOfolWztKlk3nsogdl6J0iWRjt54J9zE o9j77sH2kjF4FSPwXaBjzHs/QexSmeTkAsdLL2svpB/oSJliz9U+MhAmXwoeJB8lVmND xJaA== X-Received: by 10.224.179.67 with SMTP id bp3mr50348256qab.7.1357851762782; Thu, 10 Jan 2013 13:02:42 -0800 (PST) Received: from ph33r-retina.home (pool-100-2-123-209.nycmny.fios.verizon.net. [100.2.123.209]) by mx.google.com with ESMTPS id e12sm2257777qad.1.2013.01.10.13.02.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 13:02:41 -0800 (PST) Subject: Re: Training approval policy 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: Thu, 10 Jan 2013 16:02:35 -0500 Cc: damien clochard , Josh Berkus , PostgreSQL WWW Content-Transfer-Encoding: quoted-printable Message-Id: <792656FB-8B82-4C9A-A8C4-81AD3FAC8A91@excoventures.com> References: <50EEA591.3030905@dalibo.info> <50EEFA1C.4030508@commandprompt.com> <50EEFE57.2010505@agliodbs.com> <50EF26BD.60209@dalibo.info> To: Magnus Hagander X-Mailer: Apple Mail (2.1280) X-Gm-Message-State: ALoCoQkzCXqg7GSGF146lXs3x8wCNDsS3LKrUB6fd3jsQc3HLvuBZ8824taKh87Ys0Z1ASBIOeR/ 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 Jan 10, 2013, at 3:48 PM, Magnus Hagander wrote: > On Thu, Jan 10, 2013 at 9:38 PM, damien clochard wro= te: >> Le 10/01/2013 19:14, Magnus Hagander a =E9crit : >>> On Thu, Jan 10, 2013 at 6:45 PM, Josh Berkus wrote: >>>>=20 >>>>> It is likely because we have in the past had lots of people advertise >>>>> training in bulk and then end up canceling most of them. >>>>=20 >>>> We did. The policy was specifically to address a couple of companies >>>> who were listing a training event every week, in order to upstage other >>>> training companies. >>>=20 >>> Yes. >>>=20 >>> An honest question to Damien though - do you actually expect to *run* >>> all these training sessions, or are you basicaly doing the same thing >>> - settings up lots of options and then plan to run the most popular >>> ones? >>>=20 >> I understand there might have been a problem before with a couple of >> trolls posting too many unlikely sessions... But this is not what we are >> doing here. We don't believe in the Google pagerank religion. We suck at >> SEO. We don't need to upstage anyone. >>=20 >> We just want to let people know what we plan to do. If that's not >> possible on postgresql.org, well nevermind. We'll find something else to >> do with our time :-) >=20 > Nah, I think we need a policy that actually helps people (both > providers and consumers), without being abuse:able. Not entirely sure > what it is. Maybe we can just increase the numbers now and it won't be > a problem, because the market has matured. Earlier in the thread, Damien suggested allowing 15-20 / quarter. Why not = start at 10 /quarter and see what happens? 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