public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Olexa <darkside@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] An official Gentoo wiki
Date: Tue, 11 Nov 2008 20:39:41 -0600	[thread overview]
Message-ID: <491A41ED.3040907@gentoo.org> (raw)
In-Reply-To: <20081111234532.GG7038@aerie.halcy0n.com>

Mark Loeser 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 have been following gentoo-wiki's new procedures and rebuild process 
and I think they are on a good track right now.

I am throwing this out there, can we ask Mike Valstar for a dump of all 
his stuff, slap it on gentoo hardware under a wiki.gentoo.org link? It 
could be a "community building" experience and offering the stability of 
gentoo hardware to a service like gentoo-wiki. Maybe also invite Mike to 
be the admin of said hardware, etc. Thoughts?

(I don't know what a community wiki would require for infra hardware, 
maybe someone will chime in)

2 cents,
Jeremy



  parent reply	other threads:[~2008-11-12  2:40 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 ` Jeremy Olexa [this message]
2008-11-12  1:54   ` [gentoo-dev] " 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=491A41ED.3040907@gentoo.org \
    --to=darkside@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