X-Original-To: pgsql-advocacy-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B7E829FB2D5 for ; Wed, 30 Aug 2006 05:14:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 04411-02 for ; Wed, 30 Aug 2006 05:14:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 702C79FB2CC for ; Wed, 30 Aug 2006 05:14:00 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 229A430E1A; Wed, 30 Aug 2006 10:13:59 +0200 (MET DST) From: Lukas Kahwe Smith X-Newsgroups: pgsql.advocacy Subject: Re: PostgreSQL rebranding Date: Wed, 30 Aug 2006 10:13:56 +0200 Organization: Hub.Org Networking Services Lines: 28 Message-ID: <44F548C4.9040304@pooteeweet.org> References: <200608291614.k7TGEq215009@momjian.us> <200608291244.52587.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org To: Josh Berkus User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) In-Reply-To: <200608291244.52587.josh@agliodbs.com> To: pgsql-advocacy@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200608/181 X-Sequence-Number: 9645 Josh Berkus schrieb: > Lukas, > >>>> Illustra, EnterpriseDB, Bizgres, BizgresMPP, Mammoth, Red Hat >>>> Database, Netezza, parACCEL > > Note that BizgresMPP, Netezza, UltraSQL and Illustra had substantial code > changes from the Postgres they branched off of. For Netezza, for example, > it would be more accurate to say that they *used* PostgreSQL code rather > than re-branding it ... Postgres comprises only about 1/4 to 1/3 of their > code according to the Netezza president. Yeah thats fine. Like I said my definition of what I am looking for is kinda fuzzy (I will try to further clarify it - I think the best approach so far has been to say anything that either tries to be a fork by renaming or that is a fork by changing/adding significant code that is not intended to be made available upstream). Anyways thanks for all the input. So should I work on this inside the newly build wiki? I guess I will just ask the maintainer for an account and I will see what happens :) Otherwise I will probably just publish the list on my open source related stuff wiki .. regards, Lukas