From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L0MqH-0008Oe-3Z for garchives@archives.gentoo.org; Wed, 12 Nov 2008 21:01:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F1ACE0432; Wed, 12 Nov 2008 21:01:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 199DDE0432 for ; Wed, 12 Nov 2008 21:01:36 +0000 (UTC) Received: from [192.168.1.116] (ip72-220-190-13.sd.sd.cox.net [72.220.190.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id E8C9064564 for ; Wed, 12 Nov 2008 21:01:33 +0000 (UTC) Message-ID: <491B4429.4020202@gentoo.org> Date: Wed, 12 Nov 2008 13:01:29 -0800 From: Josh Saddler User-Agent: Thunderbird 2.0.0.17 (X11/20081001) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] An official Gentoo wiki References: <20081111234532.GG7038@aerie.halcy0n.com> <20081112094442.GL4535@mephisto> <491AC569.50407@gentoo.org> <491AC68C.6040701@ceng.metu.edu.tr> In-Reply-To: <491AC68C.6040701@ceng.metu.edu.tr> X-Enigmail-Version: 0.95.7 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC371AC7D1FDA24CFF5DA5709" X-Archives-Salt: ca8884e9-7e28-4e19-a065-5018599d4cf8 X-Archives-Hash: 1f590d617fa0f4dc2b1048bf7b62612c This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC371AC7D1FDA24CFF5DA5709 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Gokdeniz Karadag wrote: > The wiki can be a staging ground for user contributed documents, which = can > become part of official docs after a review and cleanup by developers. =2E . . no, I'd think not. It takes time and effort to produce one of our polished, professional documents. That's duplicating the time and effort that it takes to write a decent wiki article -- pointless duplication. One of the things I'm hearing from just about every other user and developer is that users would be providing the peer review necessary to keep documents at a general level of quality. This means "let the wiki live its wiki life," which means there's no need to reformat the article as something else. If it's a decent wiki article, then it should stand on its own merits....as a wiki article, nothing else. It's a community contributed article on the community-contributed resource. That's where it belongs. Most folks have said they're okay with official Gentoo documentation and a second community-contributed resource (that may not be as accurate, tested, readable, etc.) So keep that system around. If you want to jot up a quick howto, or an article filled with individual speculation and anecdotes, keep it on the wiki. If you want a doc to be considered *the* authority on its subject (such as http://www.gentoo.org/doc/en/xfce-config.xml ;)), maintained by Gentoo developers, then submit it to the GDP via bugzilla, or provide updates to one of the docs we already have. There really is no reason why we can't have this split. There's no need to XMLify every halfway decent wiki article just because it's so much better than everything else on the wiki. Trying to do so involves an inordinate number of work hours and staff that we just don't have, not to mention greatly raising the existing maintainer burden. --------------enigC371AC7D1FDA24CFF5DA5709 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkbRCwACgkQ5aFMlhMsVyXx+ACfT1Q+QNNSIkERT7Kh5hpXU651 ieUAoIzXHKdBdFxBGrpMt2p6hBalUkA9 =JmGJ -----END PGP SIGNATURE----- --------------enigC371AC7D1FDA24CFF5DA5709--