From: Ferris McCormick <fmccor@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] An official Gentoo wiki
Date: Wed, 12 Nov 2008 00:05:07 +0000 [thread overview]
Message-ID: <20081112000507.3cac021d@anaconda.krait.us> (raw)
In-Reply-To: <20081111234532.GG7038@aerie.halcy0n.com>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
On Tue, 11 Nov 2008 18:45:32 -0500
Mark Loeser <halcy0n@gentoo.org> wrote:
> So, gentoo-wiki.com went down for a awhile and took something away from
> our users something that is useful. Its back now, but I think we should
> consider having our own official wiki that our users can contribute to.
> We already have something very similar to this on the forums, and this
> would just give the correct tool to put their documentation on.
>
> I already know some people are going to hate this idea and say that the
> documentation could be wrong, etc, so lets look at how others have
> handled this situation. It seems that Ubuntu has their own official
> documentation section and a community section where users can contribute
> to. We can put a nice big warning saying that the user documentation
> may have some errors, and that any such errors should not be directed at
> the maintainers of the package or the GDP.
>
> 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?
>
I'm for it. I think the positives --- more communications paths,
community building, providing something our users want --- outweigh the
negatives (entries might be incorrect or irrelevant or whatever). I
think it's understood that contributions might contain errors, but the
can be corrected. I don't know about Ubuntu's community section, but I
do find Wikipedia very useful even though I know it might be wrong. :)
> --
> Mark Loeser
> email - halcy0n AT gentoo DOT org
> email - mark AT halcy0n DOT com
> web - http://www.halcy0n.com
Regards,
Ferris
--
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Sparc, Userrel, Trustees)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-12 0:05 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 [this message]
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
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=20081112000507.3cac021d@anaconda.krait.us \
--to=fmccor@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