public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] An official Gentoo wiki
Date: Wed, 12 Nov 2008 11:55:15 +0930	[thread overview]
Message-ID: <491A3E8B.4090803@netspace.net.au> (raw)
In-Reply-To: <20081112002116.12e12ac2@snowmobile>

Hi,

Ciaran McCreesh wrote:
> On Tue, 11 Nov 2008 18:45:32 -0500
> Mark Loeser<halcy0n@gentoo.org>  wrote:
>> What are others feelings on this?  What issues do you see with having
>> a wiki?  Do you see anyway to resolve the issue you see with us
>> having a wiki?
>
> What will policy on articles that are horribly dangerous or outright
> wrong?

see my previous email - wikipedia looks like they're writing a robot to 
deal with "Articles that need attention"[1].  We could do the same, 
there's nothing stopping us from deleting "really bad" pages.  (archives 
are always available for someone who wants to revive and improve them).

There's also the huge amount of "Cleanup tags"[2] which I really like 
(the principle, not the huge amount).  We could tailor this however we 
wanted.

 >  Is Gentoo prepared to block or warn about articles that recommend
 > stupid things?

I think we definitely should.  Someone needs to discover that the 
article does so first!

 >  If a warning is used, what will be used to distinguish
 > between a generic "wiki, not necessarily checked by sane people" and a
 > "article known to be horrible"?

Cleanup tags!  One for each.  Nice notice written at the top of the 
article saying exactly what you've said.

> The problem with wikis is that enough of them contain enough good
> information that people assume that all of them are entirely correct.

sure, but isn't that similar to, say, a forum?

> Even if warnings are used, the assumption is often "well I was warned
> about another article too and that turned out OK so I can ignore the
> warning".

sure, some users are idiots :)  Better idiot proofing doesn't protect 
you - it only creates better idiots. (I don't have a reference for this 
one).

>  And whilst it might be OK for some people to say "well, we
> warned you, so tough luck", it makes life very difficult for developers
> who end up having to deal with hordes of users with broken systems...

I agree "tough luck" might be a response by some, so the user will go to 
the next person to help.  I don't think this would necessarily fall back 
to developers.  Just like forums, mailing lists and the current wiki, 
there is good and bad advice.  From my experience on the gentoo-user 
list, bad advice generally gets noticed and corrected reasonably 
quickly.  Even big stuffups (oops I unmerged python) are helped.

There is a good culture on the user list which still calls an idiot an 
idiot.  The common one being people using ~ARCH on a remote production 
box, then complaining it broke for a ~ related reason, adding that they 
have no physical access (it happens often enough).  The usual response 
is "you shouldn't have done it, you were warned, here's how to fix it". 
  I see no problem with this.

 >  it makes life very difficult for developers
 > who end up having to deal with hordes of users with broken systems...

The only place where I could see specific developer loading, is users 
who take their problems as a result of following bad advice to bugzilla. 
  I wouldn't expect the hordes would go there first...

Anyway, the wiki exists with all it's "bad advice" already.  Making it 
official would only improve it and hence "reduce developer loading", IMHO.


[1] http://en.wikipedia.org/wiki/Wikipedia:Pages_needing_attention
[2] http://en.wikipedia.org/wiki/Wikipedia:Cleanup_resources

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Only great masters of style can succeed in being obtuse.
		-- Oscar Wilde



  reply	other threads:[~2008-11-12  2:25 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 [this message]
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
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=491A3E8B.4090803@netspace.net.au \
    --to=iaindb@netspace.net.au \
    --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