-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> If you port the exiting wiki over, you lose independence, no?
Not really - I meant move the wiki to another completely independent
server.
> Also, I think a wiki is a major overkill. All we need is a static webpage
> that the infrastructure folks can edit, no?
> Sure, that can be implemented by a wiki, but it just seems way way more
> complicated than needed.
A wiki is nice because:
* It's dirt simple to edit
* It's easy to add and remove write permission to people
* There's an automatic history of all changes
* It allows for quick organic growth. If we want to break the "Site Status" page into "Website status" and "Mailing
listsstatus", it's east to do so.
* It has email and rss alerts built in.
* It's easier for people to find.
I'd love to see all project-related information like this in one place, and
a wiki seems like the best way to do so. No reason to make yet another
resource to maintain and keep track of.
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200711141340
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFHO0EVvJuQZxSWSsgRAw8tAJ9pRRW0XSAqVIpd5vwTNl42sCEOIQCfQjpV
F7sMRxLfDn3xFAVauXPaKwc=
=cMiQ
-----END PGP SIGNATURE-----
