public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Gentoo Wiki Project
Date: Thu, 8 Apr 2010 13:51:05 -0600	[thread overview]
Message-ID: <20100408135105.49ca2e21@gentoo.org> (raw)
In-Reply-To: g2xe117dbb91004051112y6edf96cv937801b45d8ffb75@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

On Mon, 5 Apr 2010 20:12:49 +0200
Ben de Groot <yngwin@gentoo.org> wrote:

> After the mostly positive feedback on the recent wiki discussion, we
> have now gone ahead, formed a preliminary team consisting of both
> users and developers, and put up a project page [1]. All constructive
> feedback on this new project is welcome.

why are we setting up a user wiki when a very popular one already exists?  it
seems like a complete duplication of effort.  i'm not saying don't do it, i'm
just baffled why we would.

> - moderation

can we can lock certain pages down to dev edits only?  i'd like to
document some of our policies/best practices that don't seem to be in
writing anywhere (after vetting them on the list of course).


-- 
fonts,                                            by design, by neglect
gcc-porting,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-04-08 19:50 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 ` Ryan Hill [this message]
2010-04-08 20:13   ` [gentoo-dev] " 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
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=20100408135105.49ca2e21@gentoo.org \
    --to=dirtyepic@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