X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 93BEED1E93C for ; Thu, 29 Apr 2004 15:55:26 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 20748-07 for ; Thu, 29 Apr 2004 15:55:07 -0300 (ADT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0EE95D1E93E for ; Thu, 29 Apr 2004 15:55:03 -0300 (ADT) Received: from [134.22.68.249] (dyn-68-249.tor.dsl.tht.net [134.22.68.249]) by tht.net (Postfix) with ESMTP id C458776A8C; Thu, 29 Apr 2004 14:55:07 -0400 (EDT) Subject: Re: Promoting PostgreSQL to the world. From: Rod Taylor To: Bruce Momjian Cc: Josh Berkus , "pgsql-www@postgresql.org" In-Reply-To: <200404291756.i3THudK15578@candle.pha.pa.us> References: <200404291756.i3THudK15578@candle.pha.pa.us> Content-Type: text/plain Message-Id: <1083264865.30065.354.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 29 Apr 2004 14:54:26 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/251 X-Sequence-Number: 4355 > The distinction is whether we are going to require companies to give us > money to use our name or logo. If CP, SRA, or PostgreSQL, Inc. puts the > logo on their box, is that OK? I think we need to decide how this is > going to work long-term, not just in this case. But it does depend on the specific case in question. The PostgreSQL brand should be treated carefully as those using it will be seen as representatives of the project. We should not allow others to just pick up the logo or name and run with it irregardless of past experiences with that firm or person. If RedHat, SRA, or others released a retail product under the PostgreSQL name, we should: 1. Hold them to a certain quality standard 2. Ensure it is PostgreSQL code that the product is based upon and not SQL Lite branded as PostgreSQL 8 (unlikely -- but possible) 3. Ensure they provide compensation by (for example) having a minimum of N staff dedicated to improving the public code base or marketing efforts for the life of that product. Despite everything SRA has done in the past, if a new CEO came by and said they were forking the project and taking all staff off the public project, we should not allow them to continue use of the PostgreSQL brand. This requires protecting it in the first place. SRA could not have received blanket authorization to use the logo to start with. Not only should we take a reasonable cut (in this case) but we should require a certain quality level in the product they put our logo. Nothing worse than having your logo on a T-Shirt that disintegrates during the first wash.