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 16:55:36 -0600	[thread overview]
Message-ID: <20100408165536.76cdfcc9@gentoo.org> (raw)
In-Reply-To: SNT117-W23520413AAE8221EE90FAD6160@phx.gbl

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

On Thu, 8 Apr 2010 21:37:46 +0000
Sylvain Alain <d2_racing@hotmail.com> wrote:

> 
> The official wiki can be use by powerusers who want to write some pretty good doc.
> 
> A lot of powerusers can write excellent doc on the gentoo forum right now, so they don't need to by Gentoo Dev to right excellent stuff.
> 
> I don't see your point.

They already write great stuff on http://en.gentoo-wiki.com/.  I think having
two different places to put this kind of stuff might split the contributor
base.  It'd be nice if we could either merge the two or make the official
wiki about developing with Gentoo rather than how to use Gentoo, but in any
case I'm just happy to have somewhere to stick things.


-- 
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 --]

  reply	other threads:[~2010-04-08 22:54 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 [this message]
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=20100408165536.76cdfcc9@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