From: George Prowse <george.prowse@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Gentoo Wiki Project
Date: Mon, 12 Apr 2010 14:41:07 +0100 [thread overview]
Message-ID: <4BC322F3.3080909@gmail.com> (raw)
In-Reply-To: <z2p6f8b45101004120622p752ad570z85d7960568997479@mail.gmail.com>
On 12/04/2010 14:22, Arun Raghavan wrote:
> On 12 April 2010 18:49, George Prowse<george.prowse@gmail.com> wrote:
>> On 12/04/2010 14:17, Arun Raghavan wrote:
>>>
>>> On 12 April 2010 18:43, George Prowse<george.prowse@gmail.com> wrote:
>>> [...]
>>>>
>>>> If you are arguing that the name is ambiguous then I think you are wrong.
>>>> Gentoo knows about the unofficial wiki and knows it's mission is to help
>>>> Gentoo and not to hinder it. Gentoo hardly makes a habit of Apple-like
>>>> litigation when trying to protect it's logo.
>>>
>>> I think the argument is that the wiki is not always accurate, and if
>>> perceived as the official documentation, can put is in bad light.
>>>
>> There is *always* a chance of that, official or otherwise
>
> Which the Wiki team should really be addressing before making a
> world-editable wiki.
A simple warning should suffice:
"While the Gentoo community takes a large amount of care to keep the
wiki's information correct, problems like deprecation of features,
misinformed users and vandalism can and will always be a problem with
the wiki format. If you see a problem please feel free to fix it, notify
a member of the developer team or send an email to wiki@gentoo.org"
Also adding a notice like "Gentoo takes no responsibility for when you
b0rk your box by setting the wrong CTARGET" somewhere would be good.
Those two should cover all the bases.
next prev parent reply other threads:[~2010-04-12 13:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 18:12 [gentoo-dev] [RFC] Gentoo Wiki Project Ben de Groot
2010-04-05 18:52 ` Nathan Zachary
2010-04-05 19:00 ` Alex Legler
2010-04-05 19:15 ` Markos Chandras
2010-04-05 21:37 ` Zeerak Mustafa Waseem
2010-04-05 19:45 ` Sylvain Alain
2010-04-06 2:27 ` Ravi Pinjala
2010-04-06 5:16 ` Stuart Longland
2010-04-06 13:00 ` Ben de Groot
2010-04-06 15:12 ` Zeerak Mustafa Waseem
2010-04-08 19:51 ` [gentoo-dev] " Ryan Hill
2010-04-08 20:13 ` Ben de Groot
2010-04-08 20:56 ` Ryan Hill
2010-04-08 21:37 ` Sylvain Alain
2010-04-08 22:55 ` Ryan Hill
2010-04-09 0:38 ` Sylvain Alain
2010-04-09 11:26 ` Guy Fontaine
2010-04-09 12:35 ` Maciej Mrozowski
2010-04-09 13:02 ` Ben de Groot
2010-04-09 13:19 ` Nirbheek Chauhan
2010-04-09 12:38 ` Ben de Groot
2010-04-09 17:02 ` George Prowse
2010-04-09 17:24 ` Zeerak Mustafa Waseem
2010-04-09 17:32 ` AllenJB
2010-04-09 17:52 ` Ben de Groot
2010-04-09 18:52 ` Mike Pagano
2010-04-09 17:48 ` George Prowse
2010-04-09 2:42 ` Patrick Nagel
2010-04-09 6:34 ` Duncan
2010-04-12 10:28 ` Roy Bamford
2010-04-12 11:32 ` Ben de Groot
2010-04-12 13:13 ` George Prowse
2010-04-12 13:17 ` Arun Raghavan
2010-04-12 13:19 ` George Prowse
2010-04-12 13:22 ` Arun Raghavan
2010-04-12 13:41 ` George Prowse [this message]
2010-04-12 14:01 ` Ben de Groot
2010-04-12 16:47 ` Dale
2010-04-12 18:10 ` Duncan
2010-04-12 17:59 ` Duncan
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=4BC322F3.3080909@gmail.com \
--to=george.prowse@gmail.com \
--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