-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> I fully support the use of a wiki for that (a good
> example is Greg Smith's recent pg/my comparison).
> I *do not* support the use of a wiki for final
> publication of anything aimed at end users.
Well, that's a problem - Google doesn't really care where
on the postgresql.org we stick something, or whether
it is a wiki or a techdocs or a simple HTML page.
> I also have no issue experimenting with permissions to
> help Josh and the advocacy guys, but I don't think another
> wiki is required.
It's simple really - I don't think we should allow unmoderated,
anonymous content on the postgresql.org site. Requiring an email
address slightly raises the bar, but offers little overall
protection. The bar right now is a loose web of trust - "Does
somebody know who this person is? Okay, let them edit the wiki"
The ad-hoc mechanism for implementing this could be improved,
of course, but this was an experiment. A successful one, as it
turns out: it has shown that having a wiki is an excellent way
of allowing community collaboration.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200708050803
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFGtbzzvJuQZxSWSsgRA7B7AKC7aQ75XrHhXr5e1S+B70Q2uCAHBACg5Pff
RuMyCJakuiV32BnQO/dcExA=
=rIe8
-----END PGP SIGNATURE-----
