Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRS0-0006ZZ-Gy for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2013 23:22:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TtRRz-0007DI-F4 for pgsql-www@arkaria.postgresql.org; Thu, 10 Jan 2013 23:22:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRRy-0007DD-U7 for pgsql-www@postgresql.org; Thu, 10 Jan 2013 23:22:19 +0000 Received: from delta01.pnet.xcon.it ([62.48.53.16]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TtRRs-00012L-Rd for pgsql-www@postgresql.org; Thu, 10 Jan 2013 23:22:18 +0000 Received: from localhost (localhost [127.0.0.1]) by delta01.pnet.xcon.it (Postfix) with ESMTP id 3F0A51033CF77; Fri, 11 Jan 2013 00:22:12 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at delta01.pnet.xcon.it Received: from delta01.pnet.xcon.it ([127.0.0.1]) by localhost (delta01.pnet.xcon.it [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Ia+g3OSwXqdK; Fri, 11 Jan 2013 00:22:11 +0100 (CET) Received: from Gabriele.local (host44-122-dynamic.53-79-r.retail.telecomitalia.it [79.53.122.44]) (Authenticated sender: gabriele.bartolini@devise.it) by delta01.pnet.xcon.it (Postfix) with ESMTPSA id 49C7A1033CE9D; Fri, 11 Jan 2013 00:22:11 +0100 (CET) Message-ID: <50EF4D22.1090406@2ndQuadrant.it> Date: Fri, 11 Jan 2013 00:22:10 +0100 From: Gabriele Bartolini User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Josh Berkus CC: damien clochard , Magnus Hagander , PostgreSQL WWW Subject: Re: Training approval policy on pg.org References: <50EEA591.3030905@dalibo.info> <50EEFA1C.4030508@commandprompt.com> <50EEFE57.2010505@agliodbs.com> <50EF26BD.60209@dalibo.info> <50EF3A9E.2030504@2ndQuadrant.it> <50EF46C0.7060204@agliodbs.com> In-Reply-To: <50EF46C0.7060204@agliodbs.com> Content-Type: multipart/alternative; boundary="------------080102060808010206000000" 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 This is a multi-part message in MIME format. --------------080102060808010206000000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Il 10/01/13 23:54, Josh Berkus ha scritto: > It's not a false problem. That policy was created in specific response > to a specific problem from a company which (as far as I know) still > exists and will return to abusing our system if we let them. What I meant is that the limitation is probably worse than that particular abuse. Also, Magnus confirms that after that, the way events are shown has been changed. I'd agree to limit invasive submissions (such as emails and home page communications), but frankly I still believe that the current limitation is obsolete and probably also damaging. However, in case you probably missed that part in my email, I came with a proposal of 10 courses per month per organisation. A high number, but still a upper limit. > We probably want a new policy, but it needs to be one which does not > allow casual abuse. In Italy there is a saying: "Fatta la legge, trovato l'inganno" ( every law has a loophole). I think we are better off using our time and energy in positive activities, and helping healthy, dynamic and active companies promote Postgres through training. Also, who is willing to go and check if an event is really an abuse? How would you judge that? Thank you. Ciao, Gabriele -- Gabriele Bartolini - 2ndQuadrant Italia PostgreSQL Training, Services and Support gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it --------------080102060808010206000000 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Il 10/01/13 23:54, Josh Berkus ha scritto:
It's not a false problem. That policy was created in specific response to a specific problem from a company which (as far as I know) still exists and will return to abusing our system if we let them.
What I meant is that the limitation is probably worse than that particular abuse. Also, Magnus confirms that after that, the way events are shown has been changed.

I'd agree to limit invasive submissions (such as emails and home page communications), but frankly I still believe that the current limitation is obsolete and probably also damaging.

However, in case you probably missed that part in my email, I came with a proposal of 10 courses per month per organisation. A high number, but still a upper limit.
We probably want a new policy, but it needs to be one which does not
allow casual abuse.
In Italy there is a saying: "Fatta la legge, trovato l'inganno" ( every law has a loophole). I think we are better off using our time and energy in positive activities, and helping healthy, dynamic and active companies promote Postgres through training.

Also, who is willing to go and check if an event is really an abuse? How would you judge that?

Thank you.

Ciao,
Gabriele
-- 
 Gabriele Bartolini - 2ndQuadrant Italia
 PostgreSQL Training, Services and Support
 gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
--------------080102060808010206000000--