public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AllenJB <gentoo-lists@allenjb.me.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Gentoo Wiki Project
Date: Fri, 09 Apr 2010 18:32:42 +0100	[thread overview]
Message-ID: <4BBF64BA.9070404@allenjb.me.uk> (raw)
In-Reply-To: <20100409172456.GA13726@Caemlyn.Fullrate>

On 09/04/10 18:24, Zeerak Mustafa Waseem wrote:
> Really? I understood it as the wiki being an all-purposes wiki, meaning users could (would and should) create articles on how to get some application running or how to get some setting working, and the developers will have their own "section", so to speak, where they can collaborate on various projects where a wiki would be an asset.
> It seems to me from the discussion here on the list that it is to centralize documentation (- the official docs), so that gentoo can point to the wiki and say "If it's not in our docs, maybe it's in the wiki".
> 
> I may have mistaken the actual purpose of the wiki, but then by all means, correct me :-)
> 
It has no purpose. The "official" wiki currently has no rules and no
mission statement. There's been no activity for 3 days.

...in which time the unofficial wiki got countless edits in many
languages. And my server downloaded backups 3 times (because we have a
public backup policy in place to ensure the content is never lost again
- something some people seem to like ignoring (or are just ignorant of)).

AllenJB



  reply	other threads:[~2010-04-09 17:33 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 [this message]
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
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=4BBF64BA.9070404@allenjb.me.uk \
    --to=gentoo-lists@allenjb.me.uk \
    --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