Thread: Postgres derived databases
Hi, I have started work on a list of Postgres derived databases [1]. It would probably make sense to only cover PostgreSQL derived databases, which would drop Illustra and PostgreSQL itself from the list. Also it would make sense to add to this table a number of fields: - name of the company that owns/develops the database - availability (since/until) Maybe it also makes sense to list if they contribute code back at all or not. Not sure. It might make sense to add this to the about section of the main site [2]. Its sort of marketing-ish I would say I never added anything to the PostgreSQL site, so before I go through the trouble of finding the ins and outs I wanted to get a go ahead from this list. If I do get a go ahead a few pointers about how to proceed would also be nice. regards, Lukas [1] http://oss.backendmedia.com/RDBMS/PgSQLVariants [2] http://www.postgresql.org/about/
> Hi, > > I have started work on a list of Postgres derived databases > [1]. It would probably make sense to only cover PostgreSQL > derived databases, which would drop Illustra and PostgreSQL > itself from the list. > > Also it would make sense to add to this table a number of fields: > - name of the company that owns/develops the database > - availability (since/until) > > Maybe it also makes sense to list if they contribute code > back at all or not. Not sure. > > It might make sense to add this to the about section of the > main site [2]. Its sort of marketing-ish I would say > > I never added anything to the PostgreSQL site, so before I go > through the trouble of finding the ins and outs I wanted to > get a go ahead from this list. If I do get a go ahead a few > pointers about how to proceed would also be nice. I think this sounds interesting. Your options are basicalyl either to use techdocs (which would make it really easy to add), or to create a standard page. To create a standard page, look at the stuff that's in template/ in the web cvs tree (http://gborg.postgresql.org/cgi-bin/cvsweb.cgi/portal/template/?cvsroot =pgweb) to see how they are made. //Magnus
Magnus Hagander wrote: >> Hi, >> >> I have started work on a list of Postgres derived databases >> [1]. It would probably make sense to only cover PostgreSQL >> derived databases, which would drop Illustra and PostgreSQL >> itself from the list. >> >> Also it would make sense to add to this table a number of fields: >> - name of the company that owns/develops the database >> - availability (since/until) >> >> Maybe it also makes sense to list if they contribute code >> back at all or not. Not sure. >> >> It might make sense to add this to the about section of the >> main site [2]. Its sort of marketing-ish I would say >> >> I never added anything to the PostgreSQL site, so before I go >> through the trouble of finding the ins and outs I wanted to >> get a go ahead from this list. If I do get a go ahead a few >> pointers about how to proceed would also be nice. > > I think this sounds interesting. Your options are basicalyl either to > use techdocs (which would make it really easy to add), or to create a > standard page. To create a standard page, look at the stuff that's in > template/ in the web cvs tree > (http://gborg.postgresql.org/cgi-bin/cvsweb.cgi/portal/template/?cvsroot > =pgweb) to see how they are made. Well like I said in the email I think it belongs best on the main site in the about section. If you guys agree with this, I will write a patch. regards, Lukas
> > I think this sounds interesting. Your options are basicalyl > either to > > use techdocs (which would make it really easy to add), or > to create a > > standard page. To create a standard page, look at the stuff > that's in > > template/ in the web cvs tree > > > (http://gborg.postgresql.org/cgi-bin/cvsweb.cgi/portal/template/?cvsro > > ot > > =pgweb) to see how they are made. > > Well like I said in the email I think it belongs best on the > main site in the about section. If you guys agree with this, > I will write a patch. Go for it. Unless someone else objects, that is :-) //Magnus
Lukas Kahwe Smith wrote: > It might make sense to add this to the about section of the main site > [2]. Its sort of marketing-ish I would say Yes, it's marketing the other guys. Why would we want to do that? -- Peter Eisentraut http://developer.postgresql.org/~petere/
Lukas, >> It might make sense to add this to the about section of the main site >> [2]. Its sort of marketing-ish I would say > > Yes, it's marketing the other guys. Why would we want to do that? > I think the appropriate place for this is Techdocs, so that it can be maintained by the community easily. For example, I can see a fair amout of data I'd want to add to it (like which forks are dead and which are still around). --Josh Berkus
Peter Eisentraut wrote: > Lukas Kahwe Smith wrote: >> It might make sense to add this to the about section of the main site >> [2]. Its sort of marketing-ish I would say > > Yes, it's marketing the other guys. Why would we want to do that? I put it on techdocs as per Josh's comment. As for why we should have this: It makes it clear that underneath all of these marketing supported databases runs good old PostgreSQL. Also the fact that PostgreSQL has this lively ecosystem makes it clear that its not going to go away like MySQL could if it got bought. regards, Lukas