| From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
|---|---|
| To: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: pgfoundry is down |
| Date: | 2007-11-14 18:41:52 |
| Message-ID: | 3313be0a088ed92e27b4928c8f8b7334@biglumber.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
-----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 lists status", 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(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200711141340
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFHO0EVvJuQZxSWSsgRAw8tAJ9pRRW0XSAqVIpd5vwTNl42sCEOIQCfQjpV
F7sMRxLfDn3xFAVauXPaKwc=
=cMiQ
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-11-14 18:45:12 | Re: pgfoundry is down |
| Previous Message | Joshua D. Drake | 2007-11-14 18:27:31 | Re: pgfoundry is down |