-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Magnus asks:
> Should we also move things like lists of support providers etc to the
> wiki, so the companies can put more of their info in there? Seems to
> be a pretty similar case?
I don't know. It is tempting, as it is far easier to edit the wiki than
it is to gain the rights to the catalog and then use it. My vote is
for wiki-fying the catalog and then locking the pages. (Have you ever
seen the software catalog show up in a Google search?)
>> 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.
> As long as you define where the line is between "use" and "abuse".
> Especially in the context of the community, that's not necessarily
> trivial. Some people consider the one page posted there to be abuse.
> Some people consider a single blog post including a link to a
> commercial product abuse. Others don't. So it needs to be defined -
> both for those poor bastards who are supposed to police it, and for
> those who will eventually end up getting policed because they didn't
> know where the line was. With a clear policy, it makes life easier for
> both those.
Sure, and that's why I said "blatant". I'm all for a good policy, but I
also think the project is better served in the long run with a
permissive rather than a restrictive policy. We're a non-profit project,
so to speak, but the survival and growth of commerical entities
supporting Postgres should be encouraged.
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201103012235
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1tuzgACgkQvJuQZxSWSshdbwCgvVmdMbaiepYRtWBRokNY70w5
G8gAn0stnkz1jMpinCDWtqMddTYAjzir
=T811
-----END PGP SIGNATURE-----