public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joe Peterson <lavajoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] An official Gentoo wiki
Date: Wed, 12 Nov 2008 14:04:04 -0700	[thread overview]
Message-ID: <491B44C4.9030305@gentoo.org> (raw)
In-Reply-To: <491B4429.4020202@gentoo.org>

Josh Saddler wrote:
> 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.

++  Good plan.

	-Joe




  reply	other threads:[~2008-11-12 21:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 23:45 [gentoo-dev] An official Gentoo wiki Mark Loeser
2008-11-11 23:52 ` Joe Peterson
2008-12-11  5:48   ` Donnie Berkholz
2008-11-11 23:59 ` Josh Saddler
2008-11-12  0:05 ` Ferris McCormick
2008-11-12  0:15 ` Iain Buchanan
2008-11-12  0:21 ` Ciaran McCreesh
2008-11-12  2:25   ` Iain Buchanan
2008-11-13 17:21   ` Tobias Scherbaum
2008-11-14  0:44     ` [gentoo-dev] " Duncan
2008-11-12  2:39 ` [gentoo-dev] " Jeremy Olexa
2008-11-12  1:54   ` Robin H. Johnson
2008-11-12 15:17   ` [gentoo-dev] " Christian Faulhammer
2008-11-12  9:44 ` [gentoo-dev] " Michael Hammer
2008-11-12 10:23   ` Eray Aslan
2008-11-12 12:00   ` Petteri Räty
2008-11-12 12:05     ` Gokdeniz Karadag
2008-11-12 12:49       ` Michael Hammer
2008-11-12 15:49         ` Jan Kundrát
2008-11-12 21:19           ` kashani
2008-11-12 21:29             ` Jan Kundrát
2008-11-13 18:24               ` Petteri Räty
2008-11-12 15:49         ` Ben Sanchez
2008-11-12 21:01       ` Josh Saddler
2008-11-12 21:04         ` Joe Peterson [this message]
2008-12-11  5:45   ` Donnie Berkholz
2008-11-12 23:43 ` Roy Bamford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=491B44C4.9030305@gentoo.org \
    --to=lavajoe@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox