-----BEGIN PGP SIGNED MESSAGE-----
> To clarify what I'm suggesting - I'm suggesting vendors set up a page
> about their own product somewhere on their own site, be it a wiki or
> something else. If they don't have one, on a simple google site or
> even a github wiki.
> postgresql.org will then link to this from our product catalogue,
> which is on the website, just like we do for other commercial
> products. That way we (the project) provide equal level of visibility
> for third party software, and it's entirely up to the vendor exactly
> what type of information to keep on the page/wiki.
- -1. Our software catalog is nowhere near as visible as our wiki.
> So basically the same thing, except I think the vendor should keep
> their info and postgresql link to it, rather than the other way
Not sure why the wiki can't have it as well. It's not like there is a
limit on the number of pages. Also, would this apply only to
*commercial* third-party software? Because we have things like this:
Not to mention things like this:
In short, I'd like to see more on the wiki, commerical or no, I think we're
a mature enough community to be able to self-police any blatant commercial
abuse of the wiki.
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 201102261607
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
In response to
pgsql-www by date
|Next:||From: Josh Berkus||Date: 2011-02-26 21:35:12|
|Subject: Re: Top five challenges|
|Previous:||From: Greg Sabino Mullane||Date: 2011-02-26 21:00:10|
|Subject: Re: RFC: Hosting mailing lists of 3rd party projects|