X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B72D59FB2BD for ; Tue, 19 Sep 2006 14:05:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 70131-06 for ; Tue, 19 Sep 2006 14:05:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svana.org (svana.org [125.62.87.134]) by postgresql.org (Postfix) with ESMTP id DFB0F9FB2B6 for ; Tue, 19 Sep 2006 14:05:45 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 4.50) id 1GPj2V-0002MD-J8; Wed, 20 Sep 2006 03:05:43 +1000 Date: Tue, 19 Sep 2006 19:05:43 +0200 From: Martijn van Oosterhout To: Lukas Kahwe Smith Cc: pgsql-hackers@postgresql.org Subject: Re: [pgsql-www] Developer's Wiki Message-ID: <20060919170543.GD1789@svana.org> Reply-To: Martijn van Oosterhout References: <200609161309.50052.josh@agliodbs.com> <87slirwg7w.fsf@enterprisedb.com> <450C90A0.3090105@commandprompt.com> <15070.1158455724@sss.pgh.pa.us> <20060917100538.GA14893@svana.org> <23650.1158517516@sss.pgh.pa.us> <450DA0C7.5070308@dunslane.net> <450EA3E9.9000009@pooteeweet.org> <20060918145108.GE8796@svana.org> <4510206B.5090301@pooteeweet.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cQXOx3fnlpmgJsTP" Content-Disposition: inline In-Reply-To: <4510206B.5090301@pooteeweet.org> X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kleptog@svana.org X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.078 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200609/1630 X-Sequence-Number: 91158 --cQXOx3fnlpmgJsTP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 19, 2006 at 06:52:59PM +0200, Lukas Kahwe Smith wrote: > Thinking a head (and maybe too far then we really need to at this=20 > point): So how will this work once they become "official". I assume=20 > Bruce's todo list would then link to the wiki and the editing would=20 > become more conservative? Would the status get frozen? I assume that if= =20 > the given functionality is expanded/changed in future releases then it=20 > would be done in the same document? Or would a new document be startet=20 > to detail the new development process that would simply optionally list= =20 > previous documents? Unsure. I know twiki has the possibility to add a tag to a page that restricts the users that can edit a page. I assume the same could be used here somewhere, though I am unsure how. I'm not sure it's a real problem though. What's the risk? That someone will add something to the wiki that confuses people? At the end of the day it's the patch that gets reviewed, not the wiki page. Once the patch is in it's just historical interest I guess... Have a nice day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to l= itigate. --cQXOx3fnlpmgJsTP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFECNnIB7bNG8LQkwRAnYpAJsEWxf+GYzwHyK0t5uGA6udDzrYDQCfc2UK 7tJpD68bj74GL8cQs10Q8Ho= =ep11 -----END PGP SIGNATURE----- --cQXOx3fnlpmgJsTP--