Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A39609FBF12 for ; Tue, 23 Oct 2007 15:57:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 17959-08 for ; Tue, 23 Oct 2007 15:57:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id ACDB49FBF04 for ; Tue, 23 Oct 2007 15:57:06 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO [192.168.2.3]) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 13646096 for pgsql-www@postgresql.org; Tue, 23 Oct 2007 12:01:36 -0700 From: Josh Berkus Organization: PostgreSQL @ Sun To: PostgreSQL www Subject: Training events policy ... first test case Date: Tue, 23 Oct 2007 11:58:28 -0700 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710231158.28797.josh@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/125 X-Sequence-Number: 12712 Folks, Everyone on this list who spoke up approved of the "No more than one training event per company per month" policy for training events. The purpose of this policy is to prevent training companies from messing with our events listings in order to grab the "top 3 spots" from the home page. EnterpriseDB has just submitted 3 trainings for November and 2 for December. While I believe that EDB actually plans on holding all of these trainings, it is the kind of flooding of the training listings that we're trying to prevent. How should we suggest they revise the training listings? -- Josh Berkus PostgreSQL @ Sun San Francisco